From 40bbf9e2628175b93a54ddb235d3f14343146da8 Mon Sep 17 00:00:00 2001
From: Marc Delisle
Date: Sun, 8 May 2005 12:17:12 +0000
Subject: [PATCH] explanation for bug 1164387
---
ChangeLog | 2 ++
Documentation.html | 10 ++++++++++
2 files changed, 12 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index 1e39ec4f6..6c309d3d2 100755
--- a/ChangeLog
+++ b/ChangeLog
@@ -10,6 +10,8 @@ $Source$
in db view, thanks to Herman van Rink - helmo
* server_privileges.php: add a back link to the db on which
we are checking privileges
+ * Documentation.html: FAQ 3.13 about the MySQL API having problem dealing
+ with USE followed with a db name containing an hyphen
2005-05-08 Olivier Mueller
* scripts/upgrade.pl: new script to let unix admins upgrade phpMyadmin
diff --git a/Documentation.html b/Documentation.html
index 7305ce67e..9e0cbf3cd 100755
--- a/Documentation.html
+++ b/Documentation.html
@@ -3035,6 +3035,16 @@ To create a new, empty mimetype please see libraries/transformations/template_ge
not correctly calculated. Also, sorting results of a query like
"SELECT * from table GROUP BY" ... is problematic.
+
+ [3.13] I get an error when entering USE followed by a db name
+ containing an hyphen.
+
+
+ The tests I have made with current MySQL 4.1.11 API shows that the
+ API does not accept this syntax for the USE command. Enclosing the
+ db name with backquotes works. For further confusion, no backquotes
+ are needed with command-line mysql.
+
[4. ISPs, multi-user installations ]