Closed frankhinek closed 8 months ago
Merging #20 (53372be) into main (4c07041) will not change coverage. The diff coverage is
n/a
.
Originally thought this was only a UTF-8 setting, but it's a different obscure setting wrt sorting:
LC_COLLATE affects comparisons between strings. In practice, the most visible effect is the sort order. LC_COLLATE='C' (or POSIX which is a synonym) means that it's the byte order that drives comparisons, whereas a locale in the language_REGION form means that cultural rules will drive the comparisons. https://dba.stackexchange.com/questions/94887/what-is-the-impact-of-lc-ctype-on-a-postgresql-database
Seems that the other "locale" settings can be changed after initializing the DB:
To alter the default collation order or character set classes, use the --lc-collate and --lc-ctype options. Collation orders other than C or POSIX also have a performance penalty. For these reasons it is important to choose the right locale when running initdb.
The remaining locale categories can be changed later when the server is started. You can also use --locale to set the default for all locale categories, including collation order and character set classes. https://www.postgresql.org/docs/13/app-initdb.html
This is caused by the recent addition for string prefix filtering.
static constructPrefixFilterAsRangeFilter(prefix: string): RangeFilter {
return {
gte : prefix,
lt : prefix + '\uffff',
};
}
The \uffff
is added to the end of the prefix so that the upper bounds will not go beyond the prefix. \uffff
is a character that's sorted last lexicographically.
This PR will:
dwn-sdk-js
fromv0.2.16
tov0.2.18
dwn-sql-store
from0.2.9
to0.2.10