On 6 May 2013, at 3:47pm, Staffan Tylen <staffan.ty...@gmail.com> wrote:
> I've got a SELECT clause in the following format: > > SELECT a FROM t1 > EXCEPT > SELECT a FROM t2 > ORDER BY a COLLATE myorder; > > All a's in t1 get selected (not expected). > > SELECT a FROM t1 > EXCEPT > SELECT a FROM t2 > ORDER BY a; > > All a's in t1 except the a's in t2 get selected (as expected). > > I haven't experienced any errors using COLLATE myorder in general. > Looks like a bug to me. Unless you include your collation code, it's hard to reproduce your behaviour. Can you please try to find a demonstration with a collation order that's native to SQLite ? Perhaps a three-row example using "COLLATE NOCASE" ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
