On 8/9/05, ender <[EMAIL PROTECTED]> wrote: > <copyed from a co-developer> > Dear developers, > > a while back, our project decided to switch from mysql to usage of > various SQL backends, among this sqlite3 as our favorite. Now recently > we encountered a problem, just a tiny one, but one we are not able to > solve with all used SQl backends in a common sense. > > The problem arised within a table that had a column called '0_uid'. As > you might guess, the problem comes from the beginning digit in the > column name. I looked arround quite a while and learned, that it was > pure luck that we haven't had problems with that so far - as we relied > upon an SQL extension that mySQL offered. After some reading and trying > I found out, that sqlite3 also was able to handle such columns, but the > column name has to be quoted. Ok, that sounds fair - BUT I had to learn > one sad thing... mySQL and sqlite3 don't agree upon a common subset of > symbols to quote. Whilest the one accepts ' and ", the other relies upon `. > > So my simple feature request would be: allow '`' as a quoting symbol - > as mySQL does. Or - what would be as helpful as the other idea - allow > unquoted column names with leading digits - as mySQL does.
> Also see ticket # 1337 http://www.sqlite.org/cvstrac/tktview?tn=1337 I think that supporting '`' (backquote) would be a bad idea. Then again, MySQL ignores so much of the SQL standard that I think that importing any idea from MySQL is a bad idea. -austin -- Austin Ziegler * [EMAIL PROTECTED] * Alternate: [EMAIL PROTECTED]
