On Fri, Feb 24, 2012 at 16:22, Simon Slavin wrote:
> 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 t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/02/12 07:22, Simon Slavin wrote:
> I can't find any documentation about what SQLite considers to be an
> acceptable table name.
Providing you use quotation, anything is acceptable as a table name
including zero length strings.
create table "c
On 24 Feb 2012, at 1:29pm, Benoit Mortgat 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 tab
On Fri, Feb 24, 2012 at 13:28, Don V Nielsen 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
Please, I don't mean this to be offensive. I'm not. 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
I have a database with a table name containing a quote and a space.
Let's say it's called “Ben's table”
I have created it with:
CREATE TABLE "Ben's table" ([column_spec]);
I tried the following in the SQLite shell:
.import 'file_name.txt' "Ben's table"
But that does not work. So I had
6 matches
Mail list logo
