On Fri, Feb 24, 2012 at 13:28, Don V Nielsen <donvniel...@gmail.com> wrote: > Please, I don't mean this to be offensive. I'm not.
Thanks for the answer, I did not feel offended. > It was suggested that the syntax "[Ben's table]" is cumbersome. What > is really cumbersome, in my opinion, is the table name itself. The > table name includes an white space (space) and a delimiting character > (apostrophe.) The simple table name has lots of junk in it that will > throw a left hook to many language parsers. > To simplify everything, just name the table BensTable. Camel case the > words, drop the spaces. Everything is still very readable and makes > sense. I fully agree that it's not really advisable to name a table like this. Still, since SQLite supports non-"\w+" table names, 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? (Note: another workaround to import into "Ben's table" is using the octal digits escaping with backslashes:) .import my_file \042Ben's\040table\042 -- Benoit Mortgat 20, avenue Marcel Paul 69200 VĂ©nissieux, France +33 6 17 15 41 58 +33 4 27 11 61 23 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users