ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Sapego <isap...@gridgain.com>
Subject Re: Default SQL schema name
Date Mon, 29 May 2017 14:03:10 GMT
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 <sergi.vladykin@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 <vozerov@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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message