From: "n.pettik" <korablev@tarantool.org>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v2 2/2] sql: use 'view' opts from space
Date: Tue, 27 Mar 2018 14:05:02 +0300 [thread overview]
Message-ID: <60C99E00-4002-4F08-8495-4B0014B252AD@tarantool.org> (raw)
In-Reply-To: <20180327060443.GB4581@atlas>
> On 27 Mar 2018, at 09:04, Konstantin Osipov <kostja@tarantool.org> wrote:
>
> * Nikita Pettik <korablev@tarantool.org> [18/03/27 02:06]:
>>
>> +/**
>> + * Return true if space which corresponds to
>> + * given table has view option.
>> + */
>> +bool
>> +space_is_view(Table *table)
>> +{
>> + assert(table != NULL);
>> + uint32_t space_id = SQLITE_PAGENO_TO_SPACEID(table->tnum);
>> + struct space *space = space_by_id(space_id);
>> + assert(space != NULL);
>> + return space->def->opts.view;
>> +}
>
> I assume this implementation will change in a few weeks.
It’s true. Added FIXME clarification:
@@ -1163,6 +1163,10 @@ index_collation_name(Index *idx, uint32_t column)
/**
* Return true if space which corresponds to
* given table has view option.
+ *
+ * FIXME: this is temporary wrapper around SQL specific struct.
+ * It will be removed after data dictionary integration
+ * into SQL is finished.
next prev parent reply other threads:[~2018-03-27 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 23:03 [tarantool-patches] [PATCH v2 0/2] Introduce 'view' space option Nikita Pettik
2018-03-26 23:03 ` [tarantool-patches] [PATCH v2 1/2] " Nikita Pettik
2018-03-27 6:02 ` [tarantool-patches] " Konstantin Osipov
2018-03-27 11:04 ` n.pettik
2018-03-26 23:03 ` [tarantool-patches] [PATCH v2 2/2] sql: use 'view' opts from space Nikita Pettik
2018-03-27 6:04 ` [tarantool-patches] " Konstantin Osipov
2018-03-27 11:05 ` n.pettik [this message]
2018-03-27 11:35 ` [tarantool-patches] Re: [PATCH v2 0/2] Introduce 'view' space option v.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=60C99E00-4002-4F08-8495-4B0014B252AD@tarantool.org \
--to=korablev@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v2 2/2] sql: use '\''view'\'' opts from 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