00 от stanilovsky evgeny <
> estanilovs...@gridgain.com>:
> >
> >
> >
> >--- Forwarded message ---
> >From: "Vladimir Ozerov" < voze...@gridgain.com >
> >To: dev < dev@ignite.apache.org >
> >Cc: arzamas...@mail.ru
> >Sub
>
>To: dev < dev@ignite.apache.org >
>Cc: arzamas...@mail.ru
>Subject: Re: Case sensitive indexes question.
>Date: Tue, 04 Dec 2018 15:27:02 +0300
>
>I think that this is not an exceptional case, as nothing is broken.
>Throwing exception may make migration from othe
I think that this is not an exceptional case, as nothing is broken.
Throwing exception may make migration from other systems harder. Warning
should be enough.
Also remember that all SQL caches already have 1-2 automatic indexes out of
the box, and we haven't seen much performance complaints about t
Zhenya,
Vladimir suggested not to restrict anything. However, my opinion is to
throw exception on duplicating indexes. We should better add ability to
rename index if it can be useful for anyone. Having same field set indexed
with same index type is pretty strange and adds a lot of risk for
perfor
kiy
>:
>
>
>
>--- Forwarded message ---
>From: "Vladimir Ozerov" < voze...@gridgain.com >
>To: dev < dev@ignite.apache.org >
>Cc:
>Subject: Re: Case sensitive indexes question.
>Date: Wed, 28 Nov 2018 23:11:50 +0300
>
>Hi Zhenya,
>
Hi Zhenya,
Answering your questions:
1) Yes, this is expected
2) This is standard rule applicable for almost all vendors and all SQL
commands - object name without quotes is normalized to some case (upper or
lower), object name in qoutes is left as is
3) Hard to say, need to experiment with it
4)
Igniters, i found that ignite allow to create multiple case sensitive
indexes with equal fields collection, i.e. no exception and warn here:
CREATE INDEX \"title_idx\" ON books (title);
CREATE INDEX \"tiTLE_IDX\" ON books (title);
1. in this case will be created two different index structures.
