Re: Re: Bug #695 Updated: mysql_error can't fetchthe error afte the d
| From: | Manuel Lemos | Date: | Fri, 04 Sep 1998 02:39:19 +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-791@lists.php.net to get a copy of this message | ||
Hello Zeev,
On 03-Sep-98 07:20:47, you wrote:
>>>ID: 695
>>>Updated by: zeev
>>>Reported By: mlemos@acm.org
>>>Status: Closed
>>>Bug Type: MySQL related
>>>Assigned To:
>>>Comments:
>>
>>>That's correct, and is the intended and planned behavior.
>>
>>Maybe you should document this.
>I don't think so really. Any of the MySQL functions that take an optional
>link number, mysql_error() included, would not work if there's no such link
mysql_error() takes an optional link number argument? The current
documentation doesn't mention that.
BTW, what about msql_error? Does it take an optional link number argument
too?
>open. PHP only remembers the last opened link and uses it automatically if
>you don't specify a link in your function call, but if it can't find a
>link, it won't work.
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.
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?
Regards,
Manuel Lemos
E-mail: mlemos@acm.org
URL: http://www.e-na.net/the_author.html
PGP key: finger://mlemos@zeus.ci.ua.pt
--
--
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