Hi List!
Michal wrote:
I have one question: Why was in libraries/auth/config.auth.lib.php3 called PMA_mysqldie with sql parameter containing how was mysql_connect called?
Well, at the beginning the "PMA_mysqlDie()" function was used to have a xtml valid and nice MySQL error report. Maybe we could only add a setting in this function to bypass the parser when it is called because a PHP function for MySQL failed?
Loïc
______________________________________________________________________ Etudiant: Wanadoo t'offre le Pack eXtense Haut Débit soit 150,92 euros d'économies ! Clique ici : http://www.ifrance.com/_reloc/mail.etudiant
Hi
Well, at the beginning the "PMA_mysqlDie()" function was used to have a xtml valid and nice MySQL error report. Maybe we could only add a setting in this function to bypass the parser when it is called because a PHP function for MySQL failed?
Maybe yes, but anyway we should not pass to it passwords stored in config file.
Michal
Well, at the beginning the "PMA_mysqlDie()" function was used to have a xtml valid and nice MySQL error report. Maybe we could only add a setting in this function to bypass the parser when it is called because a PHP function for MySQL failed?
And what about a PMA_phpDie() function? imho php function failures and those of MySQL queries should be handled serperately.
Alexander
On Mon, Oct 14, 2002 at 11:19:56AM +0200, Rabus wrote:
Well, at the beginning the "PMA_mysqlDie()" function was used to have a xtml valid and nice MySQL error report. Maybe we could only add a setting in this function to bypass the parser when it is called because a PHP function for MySQL failed?
And what about a PMA_phpDie() function? imho php function failures and those of MySQL queries should be handled serperately.
I'd agree with that one.
The SQL Parser and pretty-printer should only ever be used on SQL queries, and seperating the types of error is a good move to make.
-
Lo�c -
Michal Cihar -
Rabus -
Robin Johnson