You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Pavel Konstantinov <pk...@gridgain.com> on 2015/12/23 04:17:57 UTC

sqlSchema usability question

Folks,

I'm testing https://issues.apache.org/jira/browse/IGNITE-1979 and have the
following questions:

1) why I'm cannot use cache name in queries if I set sqlSchema for cache?

2) why we cannot just use cache name as sqlSchema if sqlSchema is not set
explicitly (sqlSchema is null) and cache name is valid to use as schema
name?

-- 
Pavel Konstantinov

Re: sqlSchema usability question

Posted by Sergi Vladykin <se...@gmail.com>.
1. You are actually never use cache name in SQL, you are always use schema
name. In case when sqlSchema property is not set it is just derived from
cache name.
2. Exactly this happens right now. Property sqlSchema is optional. If you
are asking why is it always quoted and case sensitive, that is for
historical reasons and can't be changed without breaking compatibility.

Sergi

2015-12-23 6:17 GMT+03:00 Pavel Konstantinov <pk...@gridgain.com>:

> Folks,
>
> I'm testing https://issues.apache.org/jira/browse/IGNITE-1979 and have the
> following questions:
>
> 1) why I'm cannot use cache name in queries if I set sqlSchema for cache?
>
> 2) why we cannot just use cache name as sqlSchema if sqlSchema is not set
> explicitly (sqlSchema is null) and cache name is valid to use as schema
> name?
>
> --
> Pavel Konstantinov
>