Re: Best practice for if (!$stmt->execute())
| From: | Rico Secada | Date: | Tue, 26 Oct 2010 04:27:33 +0000 |
| Subject: | Re: Best practice for if (!$stmt->execute()) | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-309069@lists.php.net to get a copy of this message | ||
On Mon, 25 Oct 2010 22:56:37 -0400
Paul M Foster <paulf@quillandmouse.com> wrote:
> Bear in mind, an "error" is *never* that a query returned no data or
> data the user might consider bad.
This is an important point. When is an "error" an actual error? When is
it something that *needs* to be logged and mailed?
> Paul
>
> --
> Paul M. Foster
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>