I'm aware of the limitations of the 92 Standard, as I too have suffered the same fate. But one thing for sure, conforming to the standard certainly makes migration between "Standard" implementations somewhat simpler.
I'm not speaking standardally but speaking logically. (i.e. Mr. Spock, logical) I still feel an error message rather than an unrequested result to be much more palatable and much less potentially destructive. Fred -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Simon Slavin Sent: Tuesday, June 16, 2009 12:23 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Datatypes (D. Richard Hipp) On 16 Jun 2009, at 5:32pm, Fred Williams wrote: > Still think, logically speaking, the construct should throw an error > message, rather than make stealth changes to the expected result. I suppose it might be possible to provide SQLite with a 'conform to standard' mode you could select using a PRAGMA. However, I used to have to work entirely within SQL92 (working for a big client which insisted on standard conformance) and it was a pain: the standard lacks many features we find very useful. Simon. -- http://www.hearsay.demon.co.uk | I'd expect if a computer was involved | it all would have been much worse. No Buffy for you. | -- John "West" McKenna Leave quickly now. -- Anya | THE FRENCH WAS THERE _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
