Sounds good. Can you specify the defaults for the Create Table command?
On Fri, Jun 2, 2017 at 6:55 AM, Vladimir Ozerov
wrote:
> Regarding other comments:
> 1) Config - agree, let's have a single flat class "SqlServerConfiguration"
> to store listener config. It will be a replacement for OdbcCon
Regarding other comments:
1) Config - agree, let's have a single flat class "SqlServerConfiguration"
to store listener config. It will be a replacement for OdbcConfiguration.
2) Ok, let's allow users to create indexes on non-SQL caches. This may be
convenient in some cases.
On Thu, Jun 1, 2017 at
Dmitry, Pavel, regarding limitations:
1) Caches created through SQL should not interfere with caches created
through API and config. We do not understand all implications of this
interference for now, especially in the context of persistence, so it is
better to restrict this behavior for now. Espe
I think it makes sense to reserve IGNITE schema for future use as well.
2017-06-01 0:26 GMT+03:00 Dmitriy Setrakyan :
> Vladmir,
>
> Thanks for the detailed email. My comments are inline...
>
> On Wed, May 31, 2017 at 11:21 AM, Vladimir Ozerov
> wrote:
>
> > Folks,
> >
> > Let me summarize all r
> 3) "CREATE TABLE" creates a cache with special internal property
> "sql=true". Such cache cannot be destroyed through "Ignite.destroyCache".
> It can only be dropped through "DROP TABLE".The opposite is also holds:
> static and dynamic caches cannot be dropped through "DROP TABLE".
Hi Vladimir,
Vladmir,
Thanks for the detailed email. My comments are inline...
On Wed, May 31, 2017 at 11:21 AM, Vladimir Ozerov
wrote:
> Folks,
>
> Let me summarize all recent changes to our SQL engine which are important
> from user perspective. Please think of them and let me know if you have any
> objec
