Default SQL schema name
Locked
 
|
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 |
|
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 <[hidden email]> 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 > |
|
|
In reply to this post by Vladimir Ozerov
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 <[hidden email]>: > 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 > |
|
|
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 <[hidden email]> 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 <[hidden email]>: > > > 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 > > > |
|
+1 for ignite
пн, 29 мая 2017 г. в 17:03, Igor Sapego <[hidden email]>: > 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 <[hidden email]> > 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 <[hidden email]>: > > > > > 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 > > > > > > |
|
|
In reply to this post by Vladimir Ozerov
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: [hidden email] |
|
+1 for public
Kind regards, Alex. On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov <[hidden email]> 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: [hidden email] > >
Kind regards,
Alexander |
|
|
In reply to this post by Taras Ledkov
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 <[hidden email]> 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: [hidden email] > > -- Sergey Kozlov GridGain Systems www.gridgain.com |
|
|
If "public" is already in H2, then it makes sense to use it.
On Mon, May 29, 2017 at 5:18 PM, Sergey Kozlov <[hidden email]> 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 <[hidden email]> > 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: [hidden email] > > > > > > > -- > Sergey Kozlov > GridGain Systems > www.gridgain.com > |
|
|
+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 <[hidden email]> 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 <[hidden email]> > 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 <[hidden email]> > > 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: [hidden email] > > > > > > > > > > > > -- > > Sergey Kozlov > > GridGain Systems > > www.gridgain.com > > > -- Alexey Kuznetsov |
|
|
+1 for public
> On May 29, 2017, at 8:31 AM, Alexey Kuznetsov <[hidden email]> 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 <[hidden email]> > 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 <[hidden email]> >> 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 <[hidden email]> >>> 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: [hidden email] >>>> >>>> >>> >>> >>> -- >>> Sergey Kozlov >>> GridGain Systems >>> www.gridgain.com >>> >> > > > > -- > Alexey Kuznetsov |
«
Return to Apache Ignite Developers - Legacy Mail Archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |