ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: Default SQL schema name
Date Mon, 29 May 2017 14:21:45 GMT
If "public" is already in H2, then it makes sense to use it.

On Mon, May 29, 2017 at 5:18 PM, Sergey Kozlov <skozlov@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 <tledkov@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
>

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