Re: [PHP-DOC] cvs: phpdoc /en/reference/mysql/functions mysql-affected-rows.xml mysql-close.xml mysql-create-db.xml mysql-data-seek.xml mysql-fetch-array.xml mysql-fetch-field.xml mysql-field-name.xml mysql-get-host-info.xml mysql-get-proto-info.xml mysql-get-server-info.xml mysql-insert-id.xml mysql-query.xml From: Philip Olson (philip <email protected>)
Date: 12/01/02

Hello Sara-

This might be worth discussing before implementing
across the board, I currently don't know how I feel
but do we really want newbies to post sql errors all
over the place? I think this may be why mysql_error()
wasn't used everywhere. So let's discuss a way
to handle errors and then implement. Should we
introduce a "if debug mode = on, print error" type
philosophy? Or use trigger_error? Will all this
just add to the confusion?

Regards,
Philip

On Mon, 2 Dec 2002, Sara Golemon wrote:

> pollita Sun Dec 1 21:37:30 2002 EDT
>
> Modified files:
> /phpdoc/en/reference/mysql/functions mysql-affected-rows.xml
> mysql-close.xml
> mysql-create-db.xml
> mysql-data-seek.xml
> mysql-fetch-array.xml
> mysql-fetch-field.xml
> mysql-field-name.xml
> mysql-get-host-info.xml
> mysql-get-proto-info.xml
> mysql-get-server-info.xml
> mysql-insert-id.xml
> mysql-query.xml
> Log:
> Documentation Bug #20743. Added usage of mysql_error() to examples.
>
> 

-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php