On Mon, Nov 16, 2009 at 9:49 PM, Roger Binns <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bogdan Ureche wrote: >> I just noticed the ticket was closed without being fixed, with the following >> remark: > > I was the one who closed it and added that remark. > >> Now, I have to admit that English is not my first language, nor the second, >> but the way I see it this remark means something like: "This is not a bug, >> and if you want to find out why please ask this question in the mailing >> list. " > > Not quite :-) The CVSTRAC tracker has been closed and the replacement > mechanism is described at http://www.sqlite.org/src/wiki?name=Bug+Reports > > In cases where it was obvious that the issue was a bug then I copied it over > to the new one http://www.sqlite.org/src/timeline?n=200&y=t > > In cases like this one it is not necessarily a bug and I don't have enough > knowledge to make the call. That is why the suggestion to take it up with > this group where there are people familiar with the standard and the > behaviour of other databases. > >> So here I am asking the question here: is this a bug or not? > > Which is exactly what we want to know :-) If the SQL standard specifies it > then it is a very strong candidate for fixing. If all other databases do it > then that is also strong. When only a subset do then that is not good.
Here's what happens with mysql: $ mysql -u mysqluser -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.1.30 MySQL Community Server (GPL) mysql> select databasename.tablename.* from databasename.tablename; ERROR 1146 (42S02): Table 'databasename.tablename' doesn't exist mysql> create database databasename1; Query OK, 1 row affected (0.01 sec) mysql> connect databasename1; Connection id: 2 Current database: databasename1 mysql> create table tablename1(data varchar(2)); Query OK, 0 rows affected (0.01 sec) mysql> select databasename1.tablename1.* from databasename1.tablename1; Empty set (0.00 sec) mysql> quit; Note -- no "syntax error", instead, and plausibly: "ERROR 1146","Table 'databasename.tablename' doesn't exist". Stephan If > it alters the behaviour compared to previous SQLite versions then breaking > that backwards compatibility would require exceptionally compelling evidence. > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAksCOYAACgkQmOOfHg372QSt6ACgjAAwTucstMRp950Ce4dFjxs5 > /hgAoNtrs/2oAPab4vjaZbi1ZNkCE56E > =9tn8 > -----END PGP SIGNATURE----- > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Stephan Wehner -> http://stephan.sugarmotor.org (blog and homepage) -> http://loggingit.com -> http://www.thrackle.org -> http://www.buckmaster.ca -> http://www.trafficlife.com -> http://stephansmap.org -- http://blog.stephansmap.org _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
