Bug #11523 \d behaves different from delimiter
Submitted: 23 Jun 2005 9:10 Modified: 1 Sep 2005 0:13
Reporter: Anders Karlsson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.0.6 OS:Any (*)
Assigned to: Jim Winstead CPU Architecture:Any

[23 Jun 2005 9:10] Anders Karlsson
Description:
That delimiter doesn't work is registered in several other bugs (#5337 for example). But the \d command works differently, and for some reason seems to work better.

How to repeat:
File s1.sql:
delimiter //
create table tmp1(c1 int)
//
delimiter ;
drop table tmp1;

File s2.sql:
\d //
create table tmp1(c1 int)
//
\d ;
drop table tmp1;

$ mysql test
mysql> \. s1.sql
ERROR 1051 (42S02): Unknown table 'tmp1'
mysql> exit
$ mysql test
mysql> \. s2.sql
Query OK, 0 rows affected (0.05 sec)

Query OK, 0 rows affected (0.02 sec)

mysql> exit
[27 Jun 2005 23:29] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/26464
[6 Jul 2005 19:44] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/26736
[9 Aug 2005 19:16] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/28084
[30 Aug 2005 0:01] Jim Winstead
Fixed in 5.0.12. Built-in client commands such as delimiter and \d are now always parsed within files that are read using the  \. and source commands.
[1 Sep 2005 0:13] Paul Dubois
Noted in 5.0.12 changelog.