From: Roman Khabibov <roman.habibov@tarantool.org> To: tarantool-patches@dev.tarantool.org Cc: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v2 0/3] Add constraint names hash table to space Date: Wed, 4 Dec 2019 19:23:56 +0300 [thread overview] Message-ID: <D420D6B5-5A73-4165-999E-B90BEDA751C0@tarantool.org> (raw) In-Reply-To: <44d1754c-ee10-aac5-3fdf-66aad8b2fd70@tarantool.org> > On Nov 30, 2019, at 04:03, Vladislav Shpilevoy <v.shpilevoy@tarantool.org> wrote: > > Hi! Thanks for the patch! > > See 2 comments below! > > On 28/11/2019 19:34, Roman Khabibov wrote: >> I have made essential changes to the previous patch, so I decided >> to send it as v2. >> >> 1) I still don't understand, why we need to store constraint id. If we have the >> query "ALTER TABLE T DROP CONSTRAINT C", we just get struct space by its name, >> then find the corresponding constraint_def node by the name and emit opcode on >> replace in _index/_fk_constraint/_ck_constraint depending on >> constraint_def->type. > > 1. ID is a primary index. You can delete by ID. Is it always > possible to delete by name? Do all the constraint spaces have a > unique index over name consisting of one column? I know a space_id. So, I will delete tuples from _index, _ck, _fk by their unique composite indexes: +----------+------------+ | space_id | name/iid | +----------+------------+ If we want to delete by ID, let’s add it to _ck and _fk and keep it in struct constraint_def also. But, IMO, it is not about my patchset. >> >> 2) space_delete() >> I don't know how to check, if the hash table is empty, because it jsut freed. > > 2. Mhash provides mh_size() method. Add an assert, that it > is it == 0. Done. >> >> salad/mhash.h >> void >> _mh(delete)(struct _mh(t) *h) >> { >> if (h->shadow->p) { >> free(h->shadow->p); >> free(h->shadow->b); >> memset(h->shadow, 0, sizeof(*h->shadow)); >> } >> free(h->shadow); >> free(h->b); >> free(h->p); >> free(h); >> } >> Roman Khabibov (2): >> box: introduce constraint names hash table >> sql: make constraint operations transactional >> >> src/box/CMakeLists.txt | 1 + >> src/box/alter.cc | 427 +++++++++++++++++++++++++++++++---- >> src/box/constraint_def.c | 59 +++++ >> src/box/constraint_def.h | 83 +++++++ >> src/box/space.c | 56 +++++ >> src/box/space.h | 39 ++++ >> test/sql/constraint.result | 190 ++++++++++++++++ >> test/sql/constraint.test.lua | 84 +++++++ >> 8 files changed, 892 insertions(+), 47 deletions(-) >> create mode 100755 src/box/constraint_def.c >> create mode 100755 src/box/constraint_def.h >> create mode 100644 test/sql/constraint.result >> create mode 100755 test/sql/constraint.test.lua
next prev parent reply other threads:[~2019-12-04 16:23 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-28 18:34 [Tarantool-patches] [PATCH v2 0/2] " Roman Khabibov 2019-11-28 18:34 ` [Tarantool-patches] [PATCH v2 1/2] box: introduce constraint names hash table Roman Khabibov 2019-11-30 1:03 ` Vladislav Shpilevoy 2019-12-04 16:23 ` [Tarantool-patches] [PATCH v2 1/3] " Roman Khabibov 2019-12-07 16:34 ` Vladislav Shpilevoy 2019-12-10 12:48 ` Roman Khabibov 2019-11-28 18:34 ` [Tarantool-patches] [PATCH v2 2/2] sql: make constraint operations transactional Roman Khabibov 2019-11-29 7:38 ` Roman Khabibov 2019-11-30 1:03 ` Vladislav Shpilevoy 2019-12-04 16:23 ` [Tarantool-patches] [PATCH v2 2/3] " Roman Khabibov 2019-12-05 18:43 ` Roman Khabibov 2019-12-07 16:35 ` Vladislav Shpilevoy 2019-12-10 12:49 ` [Tarantool-patches] [PATCH v2 2/3] box: " Roman Khabibov 2019-12-15 22:26 ` Vladislav Shpilevoy 2019-12-17 15:03 ` Roman Khabibov 2019-12-28 0:18 ` Nikita Pettik 2019-12-28 11:07 ` Vladislav Shpilevoy 2019-12-29 0:07 ` Nikita Pettik 2019-12-29 15:51 ` Vladislav Shpilevoy 2019-12-29 22:28 ` Nikita Pettik 2019-12-29 22:35 ` Vladislav Shpilevoy 2019-12-30 11:12 ` Sergey Ostanevich 2019-12-30 12:05 ` Nikita Pettik 2019-12-21 20:54 ` Sergey Ostanevich 2019-12-22 14:59 ` Vladislav Shpilevoy 2019-12-24 12:06 ` Roman Khabibov 2019-11-30 1:03 ` [Tarantool-patches] [PATCH v2 0/2] Add constraint names hash table to space Vladislav Shpilevoy 2019-12-04 16:23 ` Roman Khabibov [this message] 2019-12-07 16:34 ` [Tarantool-patches] [PATCH v2 0/3] " 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=D420D6B5-5A73-4165-999E-B90BEDA751C0@tarantool.org \ --to=roman.habibov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 0/3] Add constraint names hash table to 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