Re: Re: Bug #695 Updated: mysql_error can't fetchthe error afte the d
| From: | Zeev Suraski | Date: | Fri, 04 Sep 1998 06:37:40 +0000 |
| Subject: | Re: Re: Bug #695 Updated: mysql_error can't fetchthe error afte the d | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-792@lists.php.net to get a copy of this message | ||
At 02:39 04/09/98 +0000, Manuel Lemos wrote:
>mysql_error() takes an optional link number argument? The current
>documentation doesn't mention that.
Well, it does.
>BTW, what about msql_error? Does it take an optional link number argument
>too?
No, the mSQL API isn't too bright about multiple connections.
>Ok, but since the documentation says that it returns the last error message
>returned by the backend, IMHO it would be logic that it would return the
>last error even if the respective connection was closed.
Well, since PHP doesn't store the error message but MySQL, the error text
is fetched on-demand from the MySQL server. If the link is closed before
that, it's impossible to fetch that text.
>BTW, if by any chance you have more than one connection, which one it
>fetches the error from if you don't pass any link number?
Just about any function in the MySQL API takes an optional link number, to
allow for multiple links. If you don't specify that link, the most
recently opened link is used.
Zeev
--
Zeev Suraski <zeev@php.net>
For a PGP public key, finger bourbon@netvision.net.il
--
PHP Development Mailing List http://www.php.net/
To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net
For help: php-dev-help@lists.php.net