Re: Check constrain execution timing change?
Simon Slavin <[email protected]>
| Newsgroups | gmane.comp.db.sqlite.general |
|---|---|
| Message-ID | <[email protected]> |
On 31 Jan 2020, at 10:51pm, Richard Hipp <[email protected]> wrote: > CREATE TABLE t1(x INTEGER CHECK(typeof(x)=='text')); > INSERT INTO t1 VALUES('123'); > PRAGMA integrity_check; Short and sweet. That's what I was talking about. How do you feel about that ? Should a programmer be able to create a failure in integrity_check that easily ? It's just two legit lines of SQL. My gut feeling is that it points to something wrong with SQLite. But there are lot of people here who know more about it than me. Would be interesting to see an example which depends only on features of SQL, avoiding typeof(). Might make it more obvious whether it's a bug. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users