You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
previously such code:
s = box.schema.space.create('test')
s:create_index('pk', {parts = {1, 'int'}})
s:create_index('sk', {parts = {2, is_nullable=true}})
was resulting in is_nullable=false, which is wrong
Closes#5674
previously such code:
s = box.schema.space.create('test')
s:create_index('pk', {parts = {1, 'int'}})
s:create_index('sk', {parts = {2, is_nullable=true}})
was resulting in is_nullable=false, which is wrong
Closes#5674
previously such code:
s = box.schema.space.create('test')
s:create_index('pk', {parts = {1, 'int'}})
s:create_index('sk', {parts = {2, is_nullable=true}})
was resulting in is_nullable=false, which is wrong
Closes#5674
previously such code:
s = box.schema.space.create('test')
s:create_index('pk', {parts = {1, 'int'}})
s:create_index('sk', {parts = {2, is_nullable=true}})
was resulting in is_nullable=false, which is wrong
Closes#5674
(cherry picked from commit de6c76b)
From comment on pull request:
If you create index without explicitly stating its part type, then part type options will be ignored. Example:
will result in is_nullable == false in sk.
Such index definition should be disallowed or should be supported but with correct option processing.
The text was updated successfully, but these errors were encountered: