From: "i.koptelov" <ivan.koptelov@tarantool.org>
To: tarantool-patches@freelists.org
Cc: "n.pettik" <korablev@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] sql: remove struct Table
Date: Tue, 12 Feb 2019 18:07:38 +0300 [thread overview]
Message-ID: <39164829-2624-4275-B1C5-2AC3D4680CE4@tarantool.org> (raw)
In-Reply-To: <C8BEF73E-A4C5-4BAC-B8A2-EC5AEECF1800@tarantool.org>
> On 12 Feb 2019, at 17:56, n.pettik <korablev@tarantool.org> wrote:
>
>
>
>> On 12 Feb 2019, at 16:55, i.koptelov <ivan.koptelov@tarantool.org> wrote:
>>> On 11 Feb 2019, at 20:58, n.pettik <korablev@tarantool.org> wrote:
>>>> On 6 Feb 2019, at 20:17, i.koptelov <ivan.koptelov@tarantool.org> wrote:
>>>>
>>>>>> On 1 Feb 2019, at 14:05, Ivan Koptelov<ivan.koptelov@tarantool.org> wrote:
>>>>>>
>>>>>> Thank you for the review! Sorry for all these code style errors.
>>>>>> I consider review changes minor, so I put diff b/w first and
>>>>>> second version of patch at the end of the letter.
>>>>>> (second commit on the branch 'review fixes' would be squashed)
>>>>> Don’t do it next time, pls. Instead, inline fixes as an answers to comments,
>>>>> especially when it comes for huge diff ( 209 insertions(+), 259 deletions(-))
>>>>> Otherwise, it takes a while to track fixed chunks of code in a whole diff.
>>>> Sorry for this. All review fixes below is inlined.
>>>
>>> Well, thank you. But don’t put fixes in a separate commit, at least when
>>> you push your branch to the remote repository. You may *accidentally*
>>> fail during final commit squashing and no-one will notice that.
>>>
>>> Travis status was entirely negative: It can’t be compiled.
>>> You forgot to add forward declaration of space_def.
>>> I fixed that and a couple of minor issues more. Here is a diff
>>> (I’ve squashed your commits and pushed on top of your branch).
>>>
>>> Please, check it out. If it is OK, squash them and then patch LGTM.
>> Thank you for the fixes! Ok, I would not put my fixes in separate commit in future.
>> I checked out the diff, it’s ok for me except one small issue. I’ve marked
>> it below.
>>>
>>> diff --git a/src/box/sql/sqliteInt.h b/src/box/sql/sqliteInt.h
>>> index 874fd682f..1352f6efe 100644
>>> --- a/src/box/sql/sqliteInt.h
>>> +++ b/src/box/sql/sqliteInt.h
>>> @@ -2759,6 +2760,9 @@ struct Parse {
>>> TriggerPrg *pTriggerPrg; /* Linked list of coded triggers */
>>> With *pWith; /* Current WITH clause, or NULL */
>>> With *pWithToFree; /* Free this WITH object at the end of the parse */
>>> + /** Space triggers are being coded for. */
>>> + struct space *triggered_space;
>>> + /** A space being constructed by CREATE TABLE */
>> Are you sure that this comment (last line) should be here? Is it about all lines below?
>
> I forgot to move struct space *new_space; below.
> Thanks for cross-check. Could you please fix this?
>
Fixed and pushed on branch.
next prev parent reply other threads:[~2019-02-12 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 9:54 [tarantool-patches] " Ivan Koptelov
2019-01-29 14:59 ` [tarantool-patches] " n.pettik
2019-02-01 11:05 ` Ivan Koptelov
2019-02-04 19:22 ` n.pettik
2019-02-06 17:17 ` [tarantool-patches] " i.koptelov
2019-02-11 17:58 ` [tarantool-patches] " n.pettik
2019-02-12 13:55 ` i.koptelov
2019-02-12 14:56 ` n.pettik
2019-02-12 15:07 ` i.koptelov [this message]
2019-02-15 14:47 ` 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=39164829-2624-4275-B1C5-2AC3D4680CE4@tarantool.org \
--to=ivan.koptelov@tarantool.org \
--cc=korablev@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH] sql: remove struct Table' \
/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