Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 41BD7200C84 for ; Mon, 29 May 2017 17:31:31 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4058E160BCE; Mon, 29 May 2017 15:31:31 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 87647160BC2 for ; Mon, 29 May 2017 17:31:30 +0200 (CEST) Received: (qmail 66770 invoked by uid 500); 29 May 2017 15:31:29 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 66759 invoked by uid 99); 29 May 2017 15:31:29 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 May 2017 15:31:29 +0000 Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com [209.85.220.182]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 661E61A031B for ; Mon, 29 May 2017 15:31:29 +0000 (UTC) Received: by mail-qk0-f182.google.com with SMTP id a72so50314495qkj.2 for ; Mon, 29 May 2017 08:31:29 -0700 (PDT) X-Gm-Message-State: AODbwcAPtEP0sK3+l2ouyAAc3CA7SDO5LRKIewddMViXI2yFZh7NPg1V x0OgrF8Jb00bqQqdb8O9izn/tnT8Uf1c X-Received: by 10.55.54.149 with SMTP id d143mr4420468qka.257.1496071888461; Mon, 29 May 2017 08:31:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.129.66 with HTTP; Mon, 29 May 2017 08:31:28 -0700 (PDT) In-Reply-To: References: From: Alexey Kuznetsov Date: Mon, 29 May 2017 22:31:28 +0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Default SQL schema name To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="001a1146fd4a7878170550ab61bb" archived-at: Mon, 29 May 2017 15:31:31 -0000 --001a1146fd4a7878170550ab61bb Content-Type: text/plain; charset="UTF-8" +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 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 > 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 > > 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 --001a1146fd4a7878170550ab61bb--