Puneet said: > Keep SQLite simple, and keep it compliant with whatever the single > ANSI SQL standard may be there out there.
Yes, I agree, but only because it seems that SQLite's allowance for double quotes for literals (which I have said introduces ambiguity and prevents proper error messages) seems to be for the sake of complying with a "non-standard" in MySQL. ;-) In other words, if catering for non-standards makes it worse, don't do it :-) Tom BareFeet -- ADSL2+ at the cheapest price in Australia: http://www.tandb.com.au/broadband/?sig _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
