:ext1 is one type of extension, in my case 'mp3'. I guess it doesn't make
sense when you have only one, but potentially there can be a lot more there.
('mp3', 'ogg', 'flac') etc...

Unfortunately, "COLLATION STRIP_ACCENT LIKE" doesn't seem to trigger
anything either. What makes me the most confused is that SQLite takes it as
a valid prepared statement. No error or anything.

I am using SQLite 3.3.17, which should be recent enough (latest?)

Best regards,
Jonas

On 5/25/07, Igor Tandetnik <[EMAIL PROTECTED]> wrote:

Jonas Sandman <[EMAIL PROTECTED]>
wrote:
> 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
> f.file_exists=1AND
> f.extension IN(:ext1) COLLATE STRIP_ACCENT

What do you bind to :ext1? This query doesn't make much sense to me. IN
operator requires a subselect or a list of values on the right side. If
you just have a single value in a list, why not write

f.extension = :ext1

Having said that, I believe the correct use of COLLATE clause with IN
operator should look like this:

f.extension COLLATE STRIP_ACCENT IN (value1, value2)

Igor Tandetnik



-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]

-----------------------------------------------------------------------------


Reply via email to