On Tue, 3 Sep 2013 23:50:09 +0200 Eduardo Morras <emorr...@yahoo.es> wrote:
> Don't know if column collation overrides index collation or viceversa. It's probably simpler to think of them as two things, table and index. Neither "overrides" the other. Ideally, they use the same collation. In the event not, I would think insertion would fail for any row not meeting both criteria. That is, 1. If you define a column with NOCASE and later an index without, it won't be possible to insert two values differing only by case, because the column will reject it. 2. If you define a column with default collation and later an index with NOCASE (successfully, because at the time of creation no two values differed only by case) then henceforward it *also* won't be possible to insert two values differing only by case, because the index will reject it. I suppose the current state of affairs -- where indexes have collation properties independent of the columns they index -- is more historical anomaly than design. It's hard to see a reason to carry it forward in SQLite4. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
