Hi,
is there any implications on performance of using collate i(NOCASE for
example) in the column definition when creating a table? doesn't it
effect the indexes use of those columns?
when using collate NOCASE on some column definition, how does a specific
element is chose to be returned, the
Aviad Harell [EMAIL PROTECTED] wrote:
tnx for the quick replay.
when using collate NOCASE on some column definition, how does a
specific element is chose to be returned, the upper case, the lower
case or the first one appears?
Collation doesn't affect how the data is stored, just how
Thanks to several posts in this forum, I now have a
custom collation defined with
sqlite3_create_collation, which uses Window's
CompareStringA. I managed to add it to main.c and
recompiled sqlite (I finally got my compilation
running on Windows with MingW/Msys). For my needs
properly does
Hi!
It seems that it is not possible to have a custom collation with GROUP
BY e.g.
SELECT * FROM t GROUP BY colA COLLATE NOCASE;
Is this feature maybe scheduled for an upcoming release of sqlite?
Does anybody have a suggestion for a work around other than creating the
column colA with COLLATE