> But the problem is internal logical inconsistency in datatyping. There's no internal inconsistency in SQLite. Everything is consistent and works using strict rules which are well explained in documentation and numerously discussed on this list. Just get used to the fact that SQLite works differently from other database engines.
Pavel On Thu, Apr 29, 2010 at 6:41 AM, Alexey Pechnikov <[email protected]> wrote: > 2010/4/28 Dan Bishop <[email protected]>: > ... >> Why the inconsistency? > > There are a lot of same problems. See > http://www.mail-archive.com/[email protected]/msg47832.html > sqlite> select 1='1'; > 0 > sqlite> create table test(a text); > sqlite> insert into test values (1); > sqlite> select * from test where a='1'; > 1 > sqlite> select * from test where a=1; > 1 > > So 1 can be equal to '1' and can be not. > > > My tests and dummy patch for tclsqlite > http://sqlite.mobigroup.ru/src/wiki?name=tclsqlite > But the problem is internal logical inconsistency in datatyping. As > example in PostgreSQL there is no this problem: > $ psql -h localhost --cluster 8.1/testing -U postgres template1 > > template1=> select 1='1'; > ?column? > ---------- > t > (1 row) > > -- > Best regards, Alexey Pechnikov. > http://pechnikov.tel/ > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
