On 21 Aug 2013, at 8:22pm, Igor Tandetnik <i...@tandetnik.org> wrote:
> On 8/21/2013 2:55 PM, Simon Slavin wrote: >> >> On 21 Aug 2013, at 5:02pm, Igor Tandetnik <i...@tandetnik.org> wrote: >> >>> I imagine you'd still want to be able to put COLLATE clause on the column >>> definition, as in "create table t (x collate NOCASE);". How is this >>> supposed to work in your hypothetical new world? >> >> It works the same as it does now, I think. > > Precisely. So why would you want to invent a completely different mechanism, > when you already have one and have to maintain it anyway? My problem is not with COLLATE in general. It's with expressions. Table definitions are fine. Index definitions are fine. It's purely that my understanding of the documention says that something like this "ABC" COLLATE COL1 = "3F" COLLATE COL2 should be allowed, and I don't agree. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
