Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Shcherbatov <kshcherbatov@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Nikita Pettik <korablev@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v4 8/8] sql: remove global sql_trigger hash
Date: Wed, 27 Jun 2018 21:04:39 +0300	[thread overview]
Message-ID: <02c40c29-8dec-d4dd-c645-216e14bdd5f9@tarantool.org> (raw)
In-Reply-To: <44395AB5-7067-46A9-A785-A0707686DCD9@tarantool.org>

> Typo: ‘contains’.
> It is better to say: ‘we can avoid storing AST pointers in HASH’.
Ok, tnx:
    sql: remove global sql_trigger hash
    
    As new _trigger format contains space_id, we can avoid
    storing AST pointers in HASH. Requested AST could be found
    by name in appropriate space.
    
    Part of #3273.

> Personally I would squash this commit with ’sql: move Triggers to server’,
> but it is up to you.
I'd like to keep it as is.

> You can fit index_id and name_src in one line.
-                                 int index_id,
-                                 const char *name_src,
+                                 int index_id,const char *name_src,

> And add arg names to prototype.
-void vdbe_code_drop_trigger(Parse *, SrcList *, int);
+void
+vdbe_code_drop_trigger(struct Parse *parser, struct SrcList *name, int no_err);

> I don’t see such flag.
- * present is raise_if_not_exists flag is set) in specified space.
+ * present - configure with cond_opcodeq) in specified space.
> Lets drop ‘_ptr’ suffix.
> Lets call it with ’sql_’ prefix - this function is invoked from parser
> (see for instance sql_drop_table(), sql_drop_index() etc).
-vdbe_code_drop_trigger(struct Parse *parser, struct SrcList *name, int no_err)
+sql_drop_trigger(struct Parse *parser, struct SrcList *name, int no_err)

-vdbe_code_drop_trigger_ptr(struct Parse *parser, const char *trigger_name)
+vdbe_code_drop_trigger(struct Parse *parser, const char *trigger_name)

> Redundant diff.
dropped.

  reply	other threads:[~2018-06-27 18:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1530029141.git.kshcherbatov@tarantool.org>
2018-06-26 16:13 ` [tarantool-patches] [PATCH v4 6/8] sql: refactor AST trigger object name Kirill Shcherbatov
2018-06-27 15:57   ` [tarantool-patches] " n.pettik
2018-06-27 16:35     ` Kirill Shcherbatov
2018-06-27 17:41       ` n.pettik
2018-06-27 18:04         ` Kirill Shcherbatov
2018-06-26 16:13 ` [tarantool-patches] [PATCH v4 8/8] sql: remove global sql_trigger hash Kirill Shcherbatov
2018-06-27 17:28   ` [tarantool-patches] " n.pettik
2018-06-27 18:04     ` Kirill Shcherbatov [this message]
2018-06-28 19:17       ` Vladislav Shpilevoy
2018-06-29 13:28         ` Kirill Shcherbatov
2018-06-29 13:31           ` Vladislav Shpilevoy
2018-06-29 13:54             ` Kirill Yukhin

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=02c40c29-8dec-d4dd-c645-216e14bdd5f9@tarantool.org \
    --to=kshcherbatov@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v4 8/8] sql: remove global sql_trigger hash' \
    /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