Hello, > Perhaps try the forthcoming 3.7.15 preview: > http://www.sqlite.org/sqlite3-20121009.zip > See "Please test the latest SQLite enhancements" for details: > http://comments.gmane.org/gmane.comp.db.sqlite.general/77259
Still present in that, as well. I should note (from further investigation) that this only occurs when COLLATE NOCASE is set on the fields I am joining on. My original CREATE TABLE statements should have read: CREATE TABLE SaleItem (SaleItem_ID integer NOT NULL PRIMARY KEY, SaleItem_UUID varchar NOT NULL DEFAULT '' COLLATE NOCASE, SaleItem_SaleUUID varchar NOT NULL DEFAULT '' COLLATE NOCASE, SaleItem_PictureUUID varchar NOT NULL DEFAULT '' COLLATE NOCASE); and CREATE TABLE Picture (Picture_ID integer NOT NULL PRIMARY KEY, Picture_UUID varchar NOT NULL DEFAULT '' COLLATE NOCASE, Picture_FileName varchar NOT NULL DEFAULT '' COLLATE NOCASE); I would speculate that the presence of a COLLATE is making it (incorrectly) believe that = is somehow no longer a symmetric relation (i.e. a = b doesn’t imply b = a). Best wishes, Hamish _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
