#39657 [Bgs]: The extended table-specification "database.table" creates errors

ID: 39657 User updated by: w dot kaiser at fortune dot de Reported By: w dot kaiser at fortune dot de Status: Bogus Bug Type: MySQL related Operating System: XP Pro PHP Version: 4.4.4 New Comment: Thanx for your effort! The "" around the table name (db1021924-olc`) does the trick! Previous Comments: ------------------------------------------------------------------------ [2006-11-28 09:41:09] tony2001@php.net 1) select count(*) from db1021924-olc.olc_configuration 2) select count(*) from db1021924-olc.tb1 Don't you see the difference? ------------------------------------------------------------------------ [2006-11-28 09:39:43] derick@php.net select * from db1021924-olc.olc_configuration; vs. select count(*) from db1021924-olc.olc_configuration; Do you see the difference? Honestly, you're doing something wrong yourself. It is neither a PHP problem nor a MySQL problem. ------------------------------------------------------------------------ [2006-11-28 09:30:02] w dot kaiser at fortune dot de No, it is not! I first reported the bug to the MySQL-group, but they proofed to me, that MySQl handles the situation correctly! This is what they sent to me: =============================================== Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 5 to server version: 5.0.27-community-nt Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> create database db1021924-olc; Query OK, 1 row affected (0.00 sec) mysql> use db1021924-olc; Database changed mysql> create table tb1 (id serial, col2 char(10)); Query OK, 0 rows affected (0.13 sec) mysql> insert into tb1 (col2) values ("hello") -> ; Query OK, 1 row affected (0.03 sec) mysql> select * from db1021924-olc.tb1; +----+-------+ | id | col2 | +----+-------+ | 1 | hello | +----+-------+ 1 row in set (0.00 sec) ------------------------------------------------------------------------ [2006-11-28 09:25:22] tony2001@php.net The error message comes from MySQL client, which means it's not PHP problem. ------------------------------------------------------------------------ [2006-11-28 06:29:59] w dot kaiser at fortune dot de Forgot to mention, that MySQL itself can cope with this database-name, so it must bee a PHP-problem! ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/39657 -- Edit this bug report at http://bugs.php.net/?id=39657&edit=1