Re: [sqlite] Behaviour of tables with same name

2010-05-07 Thread Jay A. Kreibich
On Fri, May 07, 2010 at 07:06:52AM -0700, a1rex scratched on the wall: > Since we are at this topic let me ask the question: Are the table > names case insensitive? $ ./sqlite3 SQLite version 3.6.23.1 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> create table T

Re: [sqlite] Behaviour of tables with same name

2010-05-07 Thread Andy Gibbs
> Since we are at this topic let me ask the question: Are the table names > case insensitive? Yes, I believe they are: as are all identifiers. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite

Re: [sqlite] Behaviour of tables with same name

2010-05-07 Thread a1rex
Since we are at this topic let me ask the question: Are the table names case insensitive? From: Andy Gibbs To: sqlite-users@sqlite.org Sent: Fri, May 7, 2010 8:00:44 AM Subject: Re: [sqlite] Behaviour of tables with same name > I think the bigger issue

Re: [sqlite] Behaviour of tables with same name

2010-05-07 Thread Andy Gibbs
> I think the bigger issue is that you probably shouldn't rely on > automatic resolution of names. ... If you're using multiple > databases-- even just temp and main-- the best solution is to > just qualify as much as you can. This is sound advice. Thank you, also, for the clarification of th

Re: [sqlite] Behaviour of tables with same name

2010-05-07 Thread Jay A. Kreibich
On Fri, May 07, 2010 at 09:43:13AM +0200, Andy Gibbs scratched on the wall: > Hi, > > I have tracked down a bug in some other software where two tables > have the same name, where it seems that the one table was masking the other. > What happens is that the table 't' in the main connection takes

[sqlite] Behaviour of tables with same name

2010-05-07 Thread Andy Gibbs
Hi, I have tracked down a bug in some other software where two tables have the same name, where it seems that the one table was masking the other. I can demonstrate simply with the following (on v3.6.23.1): create table t(i); insert into t values (1); attach database "other.db" as other; creat