Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Shcherbatov <kshcherbatov@tarantool.org>
To: tarantool-patches@freelists.org, korablev@tarantool.org
Cc: Kirill Shcherbatov <kshcherbatov@tarantool.org>
Subject: [tarantool-patches] [PATCH v1 1/2] box: fix upgrade script for _fk_constraint space
Date: Fri, 25 Jan 2019 14:12:24 +0300	[thread overview]
Message-ID: <9ddda42cee32924609b5a00707bb38da77714fe6.1548414536.git.kshcherbatov@tarantool.org> (raw)
In-Reply-To: <cover.1548414536.git.kshcherbatov@tarantool.org>

The set_system_triggers and erase routines in upgrade.lua did not
proceed actions for _fk_constraint space.
---
 src/box/lua/upgrade.lua | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/box/lua/upgrade.lua b/src/box/lua/upgrade.lua
index 3d9acc976..81f578e58 100644
--- a/src/box/lua/upgrade.lua
+++ b/src/box/lua/upgrade.lua
@@ -71,6 +71,7 @@ local function set_system_triggers(val)
     box.space._priv:run_triggers(val)
     box.space._trigger:run_triggers(val)
     box.space._collation:run_triggers(val)
+    box.space._fk_constraint:run_triggers(val)
 end
 
 --------------------------------------------------------------------------------
@@ -88,6 +89,7 @@ local function erase()
     truncate(box.space._truncate)
     truncate(box.space._collation)
     truncate(box.space._trigger)
+    truncate(box.space._fk_constraint)
     --truncate(box.space._schema)
     box.space._schema:delete('version')
     box.space._schema:delete('max_id')
-- 
2.19.2

  reply	other threads:[~2019-01-25 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 11:12 [tarantool-patches] [PATCH v1 0/2] fix 2.1.1 migration Kirill Shcherbatov
2019-01-25 11:12 ` Kirill Shcherbatov [this message]
2019-01-25 11:12 ` [tarantool-patches] [PATCH v1 2/2] box: fix Tarantool upgrade from 2.1.0 to 2.1.1 Kirill Shcherbatov
2019-01-25 11:25   ` [tarantool-patches] " Kirill Shcherbatov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ddda42cee32924609b5a00707bb38da77714fe6.1548414536.git.kshcherbatov@tarantool.org \
    --to=kshcherbatov@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH v1 1/2] box: fix upgrade script for _fk_constraint space' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox