[ 
https://issues.apache.org/jira/browse/IGNITE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5320:
------------------------------------
    Description: 
Considerations:
1) Schema is always present and is never dropped
2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache 
should reside in default schema.
3) There should be a flag on cache configuration to allow fallback to previous 
behavior, when cache existed in separate schema equal to it's name.
4) CREATE TABLE can only create objects in default schema. Throw exception 
otherwise. That is, this is OK:
{code}
CREATE TABLE "default_schema".MyTable ...
{code}

And this is not:
{code}
CREATE TABLE "non_default_schema".MyTable ...
{code}

Default schema name should be {{public}}. This is well-known name of default 
schema, and moreover it already exists in H2.

  was:
Considerations:
1) Schema is always present and is never dropped
2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache 
should reside in default schema.
3) There should be a flag on cache configuration to allow fallback to previous 
behavior, when cache existed in separate schema equal to it's name.
4) CREATE TABLE can only create objects in default schema. Throw exception 
otherwise. That is, this is OK:
{code}
CREATE TABLE "default_schema".MyTable ...
{code}

And this is not:
{code}
CREATE TABLE "non_default_schema".MyTable ...
{code}


> Add well-known SQL schema where SQL caches will "live" by default
> -----------------------------------------------------------------
>
>                 Key: IGNITE-5320
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5320
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>             Fix For: 2.1
>
>
> Considerations:
> 1) Schema is always present and is never dropped
> 2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache 
> should reside in default schema.
> 3) There should be a flag on cache configuration to allow fallback to 
> previous behavior, when cache existed in separate schema equal to it's name.
> 4) CREATE TABLE can only create objects in default schema. Throw exception 
> otherwise. That is, this is OK:
> {code}
> CREATE TABLE "default_schema".MyTable ...
> {code}
> And this is not:
> {code}
> CREATE TABLE "non_default_schema".MyTable ...
> {code}
> Default schema name should be {{public}}. This is well-known name of default 
> schema, and moreover it already exists in H2.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to