You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Vladimir Ozerov <vo...@gridgain.com> on 2017/05/29 13:54:36 UTC
Default SQL schema name
Folks,
I am going to introduce predefined SQL schema which is always accessible on
all Ignite nodes [1]. Now I am thinking on how to name. Ideas are welcomed.
My 50 cents:
1) "public" - Postgres use this name
2) "mydb" - MySQL use this name
3) "ignite" - to be aligned with our product name
4) "default" - not the way to go, since "DEFAULT" is reserved SQL keyword.
Personally I prefer "public".
Any other thoughts?
Vladimir.
[1] https://issues.apache.org/jira/browse/IGNITE-5320
Re: Default SQL schema name
Posted by Denis Magda <dm...@apache.org>.
+1 for public
> On May 29, 2017, at 8:31 AM, Alexey Kuznetsov <ak...@apache.org> wrote:
>
> +1 for public
> it make sense when copy-pasting SQL queries from ignite to H2 in order to
> check how sql works.
>
> On Mon, May 29, 2017 at 9:21 PM, Pavel Tupitsyn <pt...@apache.org>
> wrote:
>
>> If "public" is already in H2, then it makes sense to use it.
>>
>> On Mon, May 29, 2017 at 5:18 PM, Sergey Kozlov <sk...@gridgain.com>
>> wrote:
>>
>>> I vote for "public". I assume we may need "ignite" word for future as
>>> reserved word for SQL syntax extensions ...
>>>
>>> On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov <tl...@gridgain.com>
>>> wrote:
>>>
>>>> I'm OK with 'public'.
>>>>
>>>> Does the "default schema" mean (for Ignite) that all object are
>> contained
>>>> in the schema is available without a schema specification?
>>>>
>>>>
>>>>
>>>> On 29.05.2017 16:54, Vladimir Ozerov wrote:
>>>>
>>>>> Folks,
>>>>>
>>>>> I am going to introduce predefined SQL schema which is always
>> accessible
>>>>> on
>>>>> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are
>>>>> welcomed.
>>>>>
>>>>> My 50 cents:
>>>>> 1) "public" - Postgres use this name
>>>>> 2) "mydb" - MySQL use this name
>>>>> 3) "ignite" - to be aligned with our product name
>>>>> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL
>>> keyword.
>>>>>
>>>>> Personally I prefer "public".
>>>>>
>>>>> Any other thoughts?
>>>>>
>>>>> Vladimir.
>>>>>
>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-5320
>>>>>
>>>>>
>>>> --
>>>> Taras Ledkov
>>>> Mail-To: tledkov@gridgain.com
>>>>
>>>>
>>>
>>>
>>> --
>>> Sergey Kozlov
>>> GridGain Systems
>>> www.gridgain.com
>>>
>>
>
>
>
> --
> Alexey Kuznetsov
Re: Default SQL schema name
Posted by Alexey Kuznetsov <ak...@apache.org>.
+1 for public
it make sense when copy-pasting SQL queries from ignite to H2 in order to
check how sql works.
On Mon, May 29, 2017 at 9:21 PM, Pavel Tupitsyn <pt...@apache.org>
wrote:
> If "public" is already in H2, then it makes sense to use it.
>
> On Mon, May 29, 2017 at 5:18 PM, Sergey Kozlov <sk...@gridgain.com>
> wrote:
>
> > I vote for "public". I assume we may need "ignite" word for future as
> > reserved word for SQL syntax extensions ...
> >
> > On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov <tl...@gridgain.com>
> > wrote:
> >
> > > I'm OK with 'public'.
> > >
> > > Does the "default schema" mean (for Ignite) that all object are
> contained
> > > in the schema is available without a schema specification?
> > >
> > >
> > >
> > > On 29.05.2017 16:54, Vladimir Ozerov wrote:
> > >
> > >> Folks,
> > >>
> > >> I am going to introduce predefined SQL schema which is always
> accessible
> > >> on
> > >> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are
> > >> welcomed.
> > >>
> > >> My 50 cents:
> > >> 1) "public" - Postgres use this name
> > >> 2) "mydb" - MySQL use this name
> > >> 3) "ignite" - to be aligned with our product name
> > >> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL
> > keyword.
> > >>
> > >> Personally I prefer "public".
> > >>
> > >> Any other thoughts?
> > >>
> > >> Vladimir.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-5320
> > >>
> > >>
> > > --
> > > Taras Ledkov
> > > Mail-To: tledkov@gridgain.com
> > >
> > >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
> >
>
--
Alexey Kuznetsov
Re: Default SQL schema name
Posted by Pavel Tupitsyn <pt...@apache.org>.
If "public" is already in H2, then it makes sense to use it.
On Mon, May 29, 2017 at 5:18 PM, Sergey Kozlov <sk...@gridgain.com> wrote:
> I vote for "public". I assume we may need "ignite" word for future as
> reserved word for SQL syntax extensions ...
>
> On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov <tl...@gridgain.com>
> wrote:
>
> > I'm OK with 'public'.
> >
> > Does the "default schema" mean (for Ignite) that all object are contained
> > in the schema is available without a schema specification?
> >
> >
> >
> > On 29.05.2017 16:54, Vladimir Ozerov wrote:
> >
> >> Folks,
> >>
> >> I am going to introduce predefined SQL schema which is always accessible
> >> on
> >> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are
> >> welcomed.
> >>
> >> My 50 cents:
> >> 1) "public" - Postgres use this name
> >> 2) "mydb" - MySQL use this name
> >> 3) "ignite" - to be aligned with our product name
> >> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL
> keyword.
> >>
> >> Personally I prefer "public".
> >>
> >> Any other thoughts?
> >>
> >> Vladimir.
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-5320
> >>
> >>
> > --
> > Taras Ledkov
> > Mail-To: tledkov@gridgain.com
> >
> >
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>
Re: Default SQL schema name
Posted by Sergey Kozlov <sk...@gridgain.com>.
I vote for "public". I assume we may need "ignite" word for future as
reserved word for SQL syntax extensions ...
On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov <tl...@gridgain.com> wrote:
> I'm OK with 'public'.
>
> Does the "default schema" mean (for Ignite) that all object are contained
> in the schema is available without a schema specification?
>
>
>
> On 29.05.2017 16:54, Vladimir Ozerov wrote:
>
>> Folks,
>>
>> I am going to introduce predefined SQL schema which is always accessible
>> on
>> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are
>> welcomed.
>>
>> My 50 cents:
>> 1) "public" - Postgres use this name
>> 2) "mydb" - MySQL use this name
>> 3) "ignite" - to be aligned with our product name
>> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL keyword.
>>
>> Personally I prefer "public".
>>
>> Any other thoughts?
>>
>> Vladimir.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-5320
>>
>>
> --
> Taras Ledkov
> Mail-To: tledkov@gridgain.com
>
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Re: Default SQL schema name
Posted by Alexander Fedotov <al...@gmail.com>.
+1 for public
Kind regards,
Alex.
On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov <tl...@gridgain.com> wrote:
> I'm OK with 'public'.
>
> Does the "default schema" mean (for Ignite) that all object are contained
> in the schema is available without a schema specification?
>
>
>
> On 29.05.2017 16:54, Vladimir Ozerov wrote:
>
>> Folks,
>>
>> I am going to introduce predefined SQL schema which is always accessible
>> on
>> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are
>> welcomed.
>>
>> My 50 cents:
>> 1) "public" - Postgres use this name
>> 2) "mydb" - MySQL use this name
>> 3) "ignite" - to be aligned with our product name
>> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL keyword.
>>
>> Personally I prefer "public".
>>
>> Any other thoughts?
>>
>> Vladimir.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-5320
>>
>>
> --
> Taras Ledkov
> Mail-To: tledkov@gridgain.com
>
>
Re: Default SQL schema name
Posted by Taras Ledkov <tl...@gridgain.com>.
I'm OK with 'public'.
Does the "default schema" mean (for Ignite) that all object are
contained in the schema is available without a schema specification?
On 29.05.2017 16:54, Vladimir Ozerov wrote:
> Folks,
>
> I am going to introduce predefined SQL schema which is always accessible on
> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are welcomed.
>
> My 50 cents:
> 1) "public" - Postgres use this name
> 2) "mydb" - MySQL use this name
> 3) "ignite" - to be aligned with our product name
> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL keyword.
>
> Personally I prefer "public".
>
> Any other thoughts?
>
> Vladimir.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5320
>
--
Taras Ledkov
Mail-To: tledkov@gridgain.com
Re: Default SQL schema name
Posted by Dmitry Pavlov <dp...@gmail.com>.
+1 for ignite
пн, 29 мая 2017 г. в 17:03, Igor Sapego <is...@gridgain.com>:
> I like "ignite" as it has lower chance to interfere with anything
> which is already reserved.
>
> Best Regards,
> Igor
>
> On Mon, May 29, 2017 at 5:01 PM, Sergi Vladykin <se...@gmail.com>
> wrote:
>
> > PUBLIC is already default schema in H2. You can not even drop it. Oracle
> > does have PUBLIC schema as well.
> >
> > Sergi
> >
> > 2017-05-29 16:54 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Folks,
> > >
> > > I am going to introduce predefined SQL schema which is always
> accessible
> > on
> > > all Ignite nodes [1]. Now I am thinking on how to name. Ideas are
> > welcomed.
> > >
> > > My 50 cents:
> > > 1) "public" - Postgres use this name
> > > 2) "mydb" - MySQL use this name
> > > 3) "ignite" - to be aligned with our product name
> > > 4) "default" - not the way to go, since "DEFAULT" is reserved SQL
> > keyword.
> > >
> > > Personally I prefer "public".
> > >
> > > Any other thoughts?
> > >
> > > Vladimir.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-5320
> > >
> >
>
Re: Default SQL schema name
Posted by Igor Sapego <is...@gridgain.com>.
I like "ignite" as it has lower chance to interfere with anything
which is already reserved.
Best Regards,
Igor
On Mon, May 29, 2017 at 5:01 PM, Sergi Vladykin <se...@gmail.com>
wrote:
> PUBLIC is already default schema in H2. You can not even drop it. Oracle
> does have PUBLIC schema as well.
>
> Sergi
>
> 2017-05-29 16:54 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
>
> > Folks,
> >
> > I am going to introduce predefined SQL schema which is always accessible
> on
> > all Ignite nodes [1]. Now I am thinking on how to name. Ideas are
> welcomed.
> >
> > My 50 cents:
> > 1) "public" - Postgres use this name
> > 2) "mydb" - MySQL use this name
> > 3) "ignite" - to be aligned with our product name
> > 4) "default" - not the way to go, since "DEFAULT" is reserved SQL
> keyword.
> >
> > Personally I prefer "public".
> >
> > Any other thoughts?
> >
> > Vladimir.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-5320
> >
>
Re: Default SQL schema name
Posted by Sergi Vladykin <se...@gmail.com>.
PUBLIC is already default schema in H2. You can not even drop it. Oracle
does have PUBLIC schema as well.
Sergi
2017-05-29 16:54 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> Folks,
>
> I am going to introduce predefined SQL schema which is always accessible on
> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are welcomed.
>
> My 50 cents:
> 1) "public" - Postgres use this name
> 2) "mydb" - MySQL use this name
> 3) "ignite" - to be aligned with our product name
> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL keyword.
>
> Personally I prefer "public".
>
> Any other thoughts?
>
> Vladimir.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5320
>
Re: Default SQL schema name
Posted by Pavel Tupitsyn <pt...@apache.org>.
SQL Server uses "dbo", Oracle uses current user name.
I prefer "ignite". It is the only one that makes sense to me of all of the
above.
"public" - as opposed to "private"? What's the point?
Pavel
On Mon, May 29, 2017 at 4:54 PM, Vladimir Ozerov <vo...@gridgain.com>
wrote:
> Folks,
>
> I am going to introduce predefined SQL schema which is always accessible on
> all Ignite nodes [1]. Now I am thinking on how to name. Ideas are welcomed.
>
> My 50 cents:
> 1) "public" - Postgres use this name
> 2) "mydb" - MySQL use this name
> 3) "ignite" - to be aligned with our product name
> 4) "default" - not the way to go, since "DEFAULT" is reserved SQL keyword.
>
> Personally I prefer "public".
>
> Any other thoughts?
>
> Vladimir.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5320
>