 |
 |
Find a programming school near you
php4-beta | 199912
Date: 12/06/99
- Next message: Zeev Suraski: "Re: [PHP4BETA] cvs: /php4/ext/standard parsedate.y"
- Previous message: Thies C. Arntzen: "[PHP4BETA] cvs: /php4/ext/standard string.c"
- In reply to: Nick Gorham: "[PHP4BETA] ODBC and Error reporting"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Gorham wrote:
>
> Has anyone any objection to me changing the way ODBC error are
> reported, At the monment only one error is displayed, this may not be
> the error that actualy caused the fault, I am suggestion that on a
> error we keep calling SQLError until there are no more errors
> available.
>
> P.S. I promise not to change anything else this time :-)
> --
> Nick Gorham,
> Easysoft, UK.
>
Go ahead.
On a related issue: There were requests for an explicit odbc_error()
function in PHP.
I've never implemented such a function, mainly because all relevant
errors are reported as they occur and can be accessed through $PHP_ERROR
(or something like this) if error reporting was turned off. Additonally,
it would be a little bit tricky to implement such an error function,
since calling SQLError() clears the associated error, if I remember
things right. Any opinions regarding an explicit odbc_error() function?
-Andreas
-- PHP 4.0 Beta Mailing List <http://www.php.net/version4/> To unsubscribe, e-mail: php4beta-unsubscribe <email protected> For additional commands, e-mail: php4beta-help <email protected> To contact the list administrators, e-mail: php4beta-admin <email protected>
- Next message: Zeev Suraski: "Re: [PHP4BETA] cvs: /php4/ext/standard parsedate.y"
- Previous message: Thies C. Arntzen: "[PHP4BETA] cvs: /php4/ext/standard string.c"
- In reply to: Nick Gorham: "[PHP4BETA] ODBC and Error reporting"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
