explanation for bug 1164387
This commit is contained in:
@@ -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 <om@omnis.ch>
|
||||
* scripts/upgrade.pl: new script to let unix admins upgrade phpMyadmin
|
||||
|
@@ -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.
|
||||
</p>
|
||||
<h4>
|
||||
[3.13] I get an error when entering <tt>USE</tt> followed by a db name
|
||||
containing an hyphen.
|
||||
</h4>
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
||||
<a name="faqmultiuser"></a><br />
|
||||
<h3>[4. ISPs, multi-user installations ]</h3>
|
||||
|
Reference in New Issue
Block a user