Re: [sqlite] Dropping an old index

[Jacob Engstrand]

I tested some more, and apparently:

In SQLite 2.7.5, the command

	CREATE INDEX 'addressesZipIndex' ON 'addresses' (zip)

will create an index named addressesZipIndex (WITHOUT the single 
quotes.)

The command DROP INDEX addressesZipIndex (WITHOUT single quotes) will 
work as expected when running SQLite 2.7.5.
The command DROP INDEX addressesZipIndex (WITHOUT single quotes) will 
NOT work when running SQLite 2.8.13, although curiously...
...the command DROP INDEX 'addressesZipIndex' (WITH single quotes) will 
work running SQLite 2.8.13. Spooky...



In SQLite 2.8.13, the same command

	CREATE INDEX 'addressesZipIndex' ON 'addresses' (zip)

will create an index named 'addressesZipIndex' (WITH single quotes.)

The command DROP INDEX 'addressesZipIndex' (WITH single quotes) will 
work running SQLite 2.8.13.
The command DROP INDEX addressesZipIndex (WITHOUT single quotes) will 
NOT work running SQLite 2.8.13.



In SQLite 2.8.13, the command

	CREATE INDEX addressesZipIndex ON addresses (zip)

will create an index named addressesZipIndex (WITHOUT single quotes, as 
expected).

The command DROP INDEX 'addressesZipIndex' (WITH single quotes) will 
NOT work running SQLite 2.8.13.
The command DROP INDEX addressesZipIndex (WITHOUT single quotes) WILL 
work running SQLite 2.8.13, as expected.

So, sure, one could try to DROP with and without quotes and see which 
works. But is there an 'official' story here? Shouldn't CREATE INDEX 
ignore any quotes? And shouldn't both variants of DROP work, 
regardless?

/jak, sleepless in sweden (3.25 AM)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]