Re: [sqlite] Usability problem with quoted names

D. Richard Hipp wrote: > The rule in SQLite is > that a column name (or table name) can be any sequence of > characters that does not include US-ASCII punctuation or > control characters and does not begin with a digit. It is cool! I have not seen this in SQLite documentation > Note also that if

Re: [sqlite] Usability problem with quoted names

Alexander Kozlovsky <[EMAIL PROTECTED]> wrote: > Many students like gives russian names to columns, > and such columns must be double-quoted. > Have you actually tried this? SQLite is suppose to allow the use of column names containing non-roman characters without the use of double-quotes. The

Re: [sqlite] Usability problem with quoted names

Teg wrote: > Why not use "?" then fill it in the the actual value later? Quoting > and having to actually look at values to make sure they were legal > gave me no end of problems now I: > ... > I never pass any kind of quoted values any more. I'm sorry, my previous post is quite obscure. This i

Re: [sqlite] Usability problem with quoted names

Hello Alexander, Why not use "?" then fill it in the the actual value later? Quoting and having to actually look at values to make sure they were legal gave me no end of problems now I: CMutexAutolock Locker(DbLock); CDBAutoCloseCloser(&Db); CDBAutoCommit Commit(&Db);

[sqlite] Usability problem with quoted names

Hi! If I use "some double-quoted stuff" in my query, this one can have two absolutely different meanings. Usually it is column name, but if I wrote this string with error, it silently converts into string literal. I think, this silent behaviour is not very good. If it happens inside deeply nested