On 24 Feb 2012, at 1:29pm, Benoit Mortgat <mort...@gmail.com> wrote:
> I fully agree that it's not really advisable to name a table like this. > > Still, since SQLite supports non-"\w+" table names, Is this documented somewhere ? I can't find any documentation about what SQLite considers to be an acceptable table name. > I felt that the > SQLite shell should also support them in meta commands. > > If you re-read the original question, there is still the problem when > it's file names that contain spaces, apostrophes or other challenging > characters (commands affected could be: .import, .backup, .restore, > .load, .log, .output). Those cases are not that uncommon. > > If it's not planned to rewrite the argument tokenizer for meta-commands > could it be possible at least to specify in the output of .help how > those arguments are tokenized? It is faster, simpler, and would introduce far fewer ambiguities and opportunities for bugs, simply to remove the ability to create tables with whacky names. There are no real restrictions on table names in the SQL specs. You can even theoretically create a table name with a '"' or a ']' character in, if you can make the parser accepting one. So every implementation of SQL has its own peculiarities. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
