From: Kirill Yukhin <kyukhin@tarantool.org>
To: tarantool-patches@freelists.org
Cc: kostja@tarantool.org, Nikita Pettik <korablev@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] sql: make default constraint names be consistent
Date: Fri, 2 Aug 2019 14:01:17 +0300 [thread overview]
Message-ID: <20190802110117.63tnzpvhs6cdmhoj@tarantool.org> (raw)
In-Reply-To: <20190731105556.42786-1-korablev@tarantool.org>
Hello,
On 31 Jul 13:55, Nikita Pettik wrote:
> If during creation of constraint its name is not specified, then it is
> generated automatically. Occasionally, default names for each type of
> constraint turn out to be different. This patch makes them follow the
> same pattern: "shortcut"_unnamed_"table_name"_"ordinal_numb". For
> instance: fk_unnamed_T1_1 or ck_unnamed_T1_3 etc
> ---
>
> Branch: https://github.com/tarantool/tarantool/commits/np/fix-constraint-names
I've checked the patchset into master.
--
Regards, Kirill Yukhin
prev parent reply other threads:[~2019-08-02 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 10:55 [tarantool-patches] " Nikita Pettik
2019-08-01 16:42 ` [tarantool-patches] " n.pettik
2019-08-02 11:01 ` Kirill Yukhin [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=20190802110117.63tnzpvhs6cdmhoj@tarantool.org \
--to=kyukhin@tarantool.org \
--cc=korablev@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH] sql: make default constraint names be consistent' \
/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