On 16-3-2018 15:06, Vlad Khorsun via Firebird-devel wrote:
Looking at bug CORE-5774 i found very odd behavior of engine: it
seems it rebuilds
indices in many unneeded cases, when almost any property of the indexed
field is changed.
I understand that index should be rebuild in this case
And, probably, we should add:
(3) - NOT NULL is set and default value was set before
Really, why?
I don't see that as a change that would affect the existing index values.
The question was about existing NULL values. After i tried it i see that NOT
NULL will not be set in this case:
SQL>
> >> And, probably, we should add:
> >> (3) - NOT NULL is set and default value was set before
> >
> > Really, why?
> >
> > I don't see that as a change that would affect the existing index values.
>
>The question was about existing NULL values. After i tried it i see that
> NOT
> NULL will
19.03.2018 12:21, Leyne, Sean wrote:
And, probably, we should add:
(3) - NOT NULL is set and default value was set before
Really, why?
I don't see that as a change that would affect the existing index values.
The question was about existing NULL values. After i tried it i see that
NOT N
> And, probably, we should add:
> (3) - NOT NULL is set and default value was set before
Really, why?
I don't see that as a change that would affect the existing index values.
Sean
--
Check out the vibrant tech comm
19.03.2018 11:55, Leyne, Sean wrote:
Vlad,
Looking at bug CORE-5774 i found very odd behavior of engine: it seems it
rebuilds indices in many unneeded cases, when almost any property of the
indexed field is changed.
I understand that index should be rebuild in this cases only:
(1) - fi
Vlad,
>Looking at bug CORE-5774 i found very odd behavior of engine: it seems it
> rebuilds indices in many unneeded cases, when almost any property of the
> indexed field is changed.
>
>I understand that index should be rebuild in this cases only:
> (1) - field data type is changed *and*
Looking at bug CORE-5774 i found very odd behavior of engine: it seems it
rebuilds
indices in many unneeded cases, when almost any property of the indexed field
is changed.
I understand that index should be rebuild in this cases only:
- field data type is changed *and* its "index" type cha
