[patches] [schema 1/1] Allow to do not specify tail nullable index columns
kostja at tarantool.org
Fri Jan 26 00:30:19 MSK 2018
* Konstantin Osipov <kostja at tarantool.org> [18/01/26 00:27]:
> * Vladislav Shpilevoy <v.shpilevoy at tarantool.org> [18/01/25 13:59]:
> > If a column is nullable and is the last defined one (via index parts
> > or space format), it can be omited on insertion. Such absent fields
> > are treated as NULLs in comparators and are not stored.
> > Closes #2988
> Some raw thoughts:
> - maybe we should add another key part property, let's call it
> is_optional, to remove the performance impact on people not
> using the feature?
> I know this could complicate the patch quite a bit.
Some more thoughts:
- missing fields are in fact today indistinguishable from MP_NIL
keys. This feels like a pandora box, but I don't yet know why.
- how is this going to display in SQL? NULL?
- how is this going to work with json path indexes? Functional
indexes? Partial indexes?
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.org - www.twitter.com/kostja_osipov
More information about the Tarantool-patches