Re: [Modeling-users] fetch qualifier problem

[Sebastien B. <sbi...@us...>]

I wrote:
>   While making the test suite for all this and roaming around sqlite
> source code, I incidentally found an other bug
> https://sf.net/tracker/index.php?func=3Ddetail&aid=3D786217&group_id=3D58=
935&atid=3D489335
>       [ 786217 ] Qualifier LIKE can be case-insensitive
>=20
>   --> When using 'LIKE' in qualifier strings, the match for MySQL and
>   SQLite is case-*insensitive*. I did not noticed it, but the fact is
>   that sql 'LIKE' operator is by default case-insensitive for these two
>   databases.
>=20
> About SQLite: the fix for the above bug is expected to fix bug #785913:
> "LIKE qualifier w/ raw '%' and '_' does not work w/ SQLite" as well. Now
> for case insensitive match, sqlite lacks the ability to escape the
> special characters --I've submitted a patch to the sqlite ml today,
> we'll see what happens,
> cf. http://groups.yahoo.com/group/sqlite/message/4605

Both bugs have been fixed (for mysql and sqlite) and patches can be
found at:
https://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D786217&group_=
id=3D58935&atid=3D489335

  Note that the problem remains w/ sqlite and 'ilike', for the reason
  explained above.

Mario: your qualifiers with LIKE operators containing raw '%' or '_'
characters should now work as expected.

        Regards,

-- S=E9bastien.