Aviad Harell [EMAIL PROTECTED]
wrote:
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?
If you also create an index on this column, and don't explicitly specify
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 it's compared.
You will get your strings out
Jonas Sandman [EMAIL PROTECTED]
wrote:
Can I make SQLite use a collation function when making a simple query?
Before sending the data to LIKE I could override and for example
strip the accent (*á' would become 'a' and 'é' would become 'e' etc).
Recent versions of SQLite support syntax like
Thanks for the fast response Igor!
However, I tried this prepared statement:
SELECT f.fileid, f.path, m.title, m.artist, m.album, m.genre, m.comment,
m.track, m.year, m.length, m.bitrate, m.playcount, f.changed, f.size,
m.tagged FROM Files f, Meta m WHERE m.fileid=f.fileid AND
