Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Kirill Shcherbatov <kshcherbatov@tarantool.org>,
	tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v4 1/4] schema: add new system space for CHECK constraints
Date: Sun, 26 May 2019 15:03:24 +0300	[thread overview]
Message-ID: <37f6781a-1317-bca3-5c08-c2b67fc45073@tarantool.org> (raw)
In-Reply-To: <6780ecce-2186-9f6c-6b4e-133ad98ddafa@tarantool.org>

>>> + * To perform it transactionally, we create a list of a new ck
>>
>> 5. 'a' article is never used with plural.
> It is not plural here. A list ...

Somewhy you trimmed the context, but here it is again:

    "we create a list of a new ck constraints objects"

You wrote "a new ck constraints objects". Firstly, "a objects"
is incorrect. Secondly, if you want to describe an object as
purposed to something, you do not need plural. It should be

    "we create a list of new ck constraint objects"

"constraints" -> "constraint", it is like an adjective here.
"a objects" -> "objects". You can't use 'a' with plural.

>>> +		/*
>>> +		 * FIXME: Ck constraint creation on non-empty
>>> +		 * space must be implemented as preparatory
>>> +		 * step for ALTER SPACE ADD CONSTRAINT feature.
>>
>> 8. We already have ADD CONSTRAINT. It works for FK, UNIQUE, PK. The
>> problem is that we can't call it on a non-empty space.
> https://github.com/tarantool/tarantool/issues/4243

My comment was rather about incorrect comment - "ADD CONSTRAINT"
is already implemented, but here you state, that it is not so. The
comment is still incorrect.

  reply	other threads:[~2019-05-26 12:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 13:56 [tarantool-patches] [PATCH v4 0/4] box: run checks on insertions in LUA spaces Kirill Shcherbatov
2019-05-16 13:56 ` [tarantool-patches] [PATCH v4 1/4] schema: add new system space for CHECK constraints Kirill Shcherbatov
2019-05-19 16:01   ` [tarantool-patches] " Vladislav Shpilevoy
2019-05-23 10:32     ` Kirill Shcherbatov
2019-05-26 12:03       ` Vladislav Shpilevoy [this message]
2019-05-31 13:45         ` Kirill Shcherbatov
2019-05-16 13:56 ` [tarantool-patches] [PATCH v4 2/4] box: run check constraint tests on space alter Kirill Shcherbatov
2019-05-19 16:02   ` [tarantool-patches] " Vladislav Shpilevoy
2019-05-23 10:37     ` Kirill Shcherbatov
2019-05-16 13:56 ` [tarantool-patches] [PATCH v4 3/4] box: introduce column_mask for ck constraint Kirill Shcherbatov
2019-05-19 16:02   ` [tarantool-patches] " Vladislav Shpilevoy
2019-05-23 10:38     ` Kirill Shcherbatov
2019-05-26 12:03     ` Vladislav Shpilevoy
2019-05-31 13:45       ` Kirill Shcherbatov
2019-05-16 13:56 ` [tarantool-patches] [PATCH v4 4/4] box: user-friendly interface to manage ck constraints Kirill Shcherbatov
2019-05-19 16:02   ` [tarantool-patches] " Vladislav Shpilevoy
2019-05-23 10:41     ` Kirill Shcherbatov
2019-05-26 12:04       ` Vladislav Shpilevoy
2019-05-31 13:45         ` Kirill Shcherbatov
2019-06-03 21:15           ` 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=37f6781a-1317-bca3-5c08-c2b67fc45073@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=kshcherbatov@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v4 1/4] 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