|
[
Permalink
| « Hide
]
Aleksey Timohin added a comment - 09/Sep/10 03:38 PM
updated
added script and DB backup
Please test the next (tomorrow's) snapshot build. Note that you'll have to recreate all indices existing for WIN1257_LV columns, or backup/restore the database.
Tested (on 2.5.1). Work as described. Thank you.
But there is another issue: Custom created collation with ACCENT INSENSITIVE still work in the same way as ACCENT SENSITIVE collation. F.e.: CREATE COLLATION my_lv2 FOR WIN1257 from win1257_lv no pad CASE INSENSITIVE ACCENT INSENSITIVE; select * from TEST_LV_SORT tls order by tls.text COLLATE my_lv2; Query result records will be ordered using accented characters rules. This bug is not actual and not vital for us, but it exist. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||