John Stanton wrote: > That ia a nice idea. To have a pragma which specied the dialect. There > could be "strict" or "ansi" and "mysql", "oracle", "sqlserver" etc etc. > It would give tighter control over hard to track annoying minor syntax > errors. >
I don't think we need anything that involved. Just a simple standard SQL mode and a the current SQLite mode with all its extensions in place. The second is needed as the default case for backward compatibility. The first would let those who care move to standard SQL syntax. I would further suggest that SQLite could change its behavior when the next major version release happens, and make the standard mode the default, since it is allowed to break backwards compatibility at that time. Users migrating from other databases generally have to make some modifications to their schema and SQL code since none of these systems are fully standard compliant, and most have some extensions that are not supported elsewhere. It would be relatively easy to make the changes needed to use standard SQL quoting when migrating to SQLite at that point. All these database products are continually moving to better support for the SQL standard. This would simply be another step along that road. Once the database is converted to use standard quoting in SQLite it would be portable to any of the other databases since they all support standard quoting. Similarly, databases created in SQLite using standard quoting would be more easily portable to any of these other databases if the need arises. Dennis Cote _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
