From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: v.shpilevoy@tarantool.org,
Kirill Shcherbatov <kshcherbatov@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v3 1/3] schema: add new system space for CHECK constraints
Date: Tue, 14 May 2019 21:29:00 +0300 [thread overview]
Message-ID: <20190514182900.GC3801@atlas> (raw)
In-Reply-To: <bc474ef87405ea45c4c4f98298c04e9683db96a6.1557845850.git.kshcherbatov@tarantool.org>
* Kirill Shcherbatov <kshcherbatov@tarantool.org> [19/05/14 18:04]:
> This patch introduces a new system space to persist check
> constraints. Format of the space:
>
> _ck_constraint (space id = 357)
> [<constraint name> STR, <space id> UINT,
> <is_deferred>BOOL, <expression string>STR]
Please make sure at least the space definition contains all the
fields necessary for information_schema, even if this patch
doesn't fill in some of the fields yet.
Does it? What's in information_schema.check_constraints? What do
other vendors store in this system space (like deferrable,
initially deferred).
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
next prev parent reply other threads:[~2019-05-14 18:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 15:02 [tarantool-patches] [PATCH v3 0/3] box: run checks on insertions in LUA spaces Kirill Shcherbatov
2019-05-14 15:02 ` [tarantool-patches] [PATCH v3 1/3] schema: add new system space for CHECK constraints Kirill Shcherbatov
2019-05-14 18:29 ` Konstantin Osipov [this message]
2019-05-14 15:02 ` [tarantool-patches] [PATCH v3 2/3] box: run check constraint tests on space alter Kirill Shcherbatov
2019-05-14 15:02 ` [tarantool-patches] [PATCH v3 3/3] box: user-friendly interface to manage ck constraints Kirill Shcherbatov
2019-05-14 20:09 ` [tarantool-patches] " Konstantin Osipov
2019-05-14 17:00 ` [tarantool-patches] Re: [PATCH v3 0/3] box: run checks on insertions in LUA spaces Konstantin Osipov
[not found] ` <FB4C0C9D-E56E-4FEF-A2C5-87AD8BF634F9@gmail.com>
2019-05-14 18:22 ` n.pettik
2019-05-14 18:41 ` Konstantin Osipov
2019-05-14 18:49 ` n.pettik
2019-05-15 8:37 ` Kirill Shcherbatov
2019-05-16 13:51 ` Kirill Shcherbatov
2019-05-19 16:02 ` Vladislav Shpilevoy
-- strict thread matches above, loose matches on Subject: below --
2019-04-16 13:51 [tarantool-patches] " Kirill Shcherbatov
2019-04-16 13:51 ` [tarantool-patches] [PATCH v3 1/3] schema: add new system space for CHECK constraints Kirill Shcherbatov
2019-04-25 20:38 ` [tarantool-patches] " n.pettik
2019-05-07 9:53 ` Kirill Shcherbatov
2019-05-12 13:45 ` n.pettik
2019-05-12 15:52 ` Kirill Shcherbatov
2019-05-12 23:04 ` n.pettik
2019-05-13 7:11 ` Kirill Shcherbatov
2019-05-13 12:29 ` n.pettik
2019-05-13 13:13 ` Vladislav Shpilevoy
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=20190514182900.GC3801@atlas \
--to=kostja@tarantool.org \
--cc=kshcherbatov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH v3 1/3] schema: add new system space for CHECK constraints' \
/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