From: "n.pettik" <korablev@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] sql: rfc for foreign keys
Date: Fri, 13 Jul 2018 16:53:11 +0300 [thread overview]
Message-ID: <A71C0FA3-26FB-4189-829E-22AD62D28B8D@tarantool.org> (raw)
In-Reply-To: <20180713084647.GA20490@chai>
>> Part of #3271
>> ---
>> Branch: https://github.com/tarantool/tarantool/tree/np/gh-3271-foreign-keys-rfc
>> Issue: https://github.com/tarantool/tarantool/issues/3271
>>
>
> Please check with definition schema in the standard re table
> structure for information schema and constraint tables.
>
> --
> Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
> http://tarantool.io - www.twitter.com/kostja_osipov
Well, actually I didn’t get well what you mean.
If you ask to make _fk_constraint table itself be closer to REFERENTIAL_CONSTRAINTS
from ANSI schema definition.. The best effort I am able to do now - rename it to
_referential_constraints..
See part 11 of 2003 standard: 6.3.3 REFERENTIAL_CONSTRAINTS base table:
All parts which we already have in Tarantool are represented in _fk_constraints.
Others such as CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA are omitted.
Moreover, it stores fields which are absent in ANSI: is_deferred and array of links.
IDK how to remove them from those space and persist at the same time.
If you suggest to implement additional table to represent FK constraints, then
I guess it makes no sense - we don’t have any of schema tables right now.
prev parent reply other threads:[~2018-07-13 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 13:11 [tarantool-patches] " Nikita Pettik
2018-06-27 13:13 ` [tarantool-patches] " Vladislav Shpilevoy
2018-06-27 13:38 ` n.pettik
2018-06-28 8:31 ` Konstantin Osipov
2018-07-13 8:46 ` Konstantin Osipov
2018-07-13 13:53 ` n.pettik [this message]
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=A71C0FA3-26FB-4189-829E-22AD62D28B8D@tarantool.org \
--to=korablev@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH] sql: rfc for foreign keys' \
/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