> >> dsc_length is currently the descriptor's physical length. With the > >> change it will represent a logical length. To support that I added > >> getPhysicalLength() method to struct dsc returning an unsigned 32-bit > >> that sums +2/+1 for dtype_varying/dtype_cstring. > > > > During such cleanup may be make DSC fields private? > > > > What;s also worth taking into an account - what to do if user tries to > > include such huge field in an index. > > > > We already have this problem: > > SQL> create table t (c varchar(32765)); > SQL> create index t_c on t (c); > Statement failed, SQLSTATE = 42000 > unsuccessful metadata update > -CREATE INDEX T_C failed > -key size too big for index T_C
Given that the max size of an index is not related to the max size of any datatype, how does increasing max varchar solve the that use case? Sean Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
