If the environment variable ydb_lct_stdnull environment variable has the value 1, YottaDB uses standard collation for empty string (null) subscripts of local variables, i.e., the empty string collates first, before all numeric values. If set to 0, YottaDB uses the legacy collation, where the empty string collates between numeric and non-empty string subscripts. If the environment variable is not set, YottaDB uses the gtm_lct_stdnull environment variable, and if neither is set, YottaDB uses standard collation. Previously, the ydb_lct_stdnull environment variable was not recognized, and the default of legacy collation (which is not used by any application we know of) was an opportunity for an application to have an obscure, hard to troubleshoot, bug. YottaDB strongly recommends against use of legacy collation. [#113]
Description
The legacy null collation is not used by any known application, and the fact that it is the default is an opportunity for an application to have an obscure, hard to troubleshoot, bug. Standard should be the default, and the legacy should require explicit setting.
Draft Release Note
If the environment variable ydb_lct_stdnull environment variable has the value 1, YottaDB uses standard collation for empty string (null) subscripts of local variables, i.e., the empty string collates first, before all numeric values. If set to 0, YottaDB uses the legacy collation, where the empty string collates between numeric and non-empty string subscripts. If the environment variable is not set, YottaDB uses the gtm_lct_stdnull environment variable, and if neither is set, YottaDB uses standard collation. Previously, the ydb_lct_stdnull environment variable was not recognized, and the default of legacy collation (which is not used by any application we know of) was an opportunity for an application to have an obscure, hard to troubleshoot, bug. YottaDB strongly recommends against use of legacy collation. [#113]
Final Release Note
If the environment variable ydb_lct_stdnull environment variable has the value 1, YottaDB uses standard collation for empty string (null) subscripts of local variables, i.e., the empty string collates first, before all numeric values. If set to 0, YottaDB uses the legacy collation, where the empty string collates between numeric and non-empty string subscripts. If the environment variable is not set, YottaDB uses the gtm_lct_stdnull environment variable, and if neither is set, YottaDB uses standard collation. Previously, the ydb_lct_stdnull environment variable was not recognized, and the default of legacy collation (which is not used by any application we know of) was an opportunity for an application to have an obscure, hard to troubleshoot, bug. YottaDB strongly recommends against use of legacy collation. [#113]
Description
The legacy null collation is not used by any known application, and the fact that it is the default is an opportunity for an application to have an obscure, hard to troubleshoot, bug. Standard should be the default, and the legacy should require explicit setting.
Draft Release Note
If the environment variable ydb_lct_stdnull environment variable has the value 1, YottaDB uses standard collation for empty string (null) subscripts of local variables, i.e., the empty string collates first, before all numeric values. If set to 0, YottaDB uses the legacy collation, where the empty string collates between numeric and non-empty string subscripts. If the environment variable is not set, YottaDB uses the gtm_lct_stdnull environment variable, and if neither is set, YottaDB uses standard collation. Previously, the ydb_lct_stdnull environment variable was not recognized, and the default of legacy collation (which is not used by any application we know of) was an opportunity for an application to have an obscure, hard to troubleshoot, bug. YottaDB strongly recommends against use of legacy collation. [#113]