Re: Error handling strategies (db related)
| From: | Gary . | Date: | Tue, 27 Apr 2010 14:04:03 +0000 |
| Subject: | Re: Error handling strategies (db related) | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-304654@lists.php.net to get a copy of this message | ||
On Tue, Apr 27, 2010 at 10:46 AM, Peter Lind wrote:
> On 27 April 2010 10:42, Gary . wrote:
>> How do you guys handle errors during, say, db insertions.
>>
>> Let's say you have an ongoing transaction which fails on the n-th
>> insert. Ok, you roll back the transaction, no problem. How do you then
>> inform the user? Just using the text from pg_result_error or
>> something?
>>
>
> If it's a normal user, give them some info about what went wrong but
> not the specific error returned.
Yeah. I know :( Originally I couldn't find a "nice" way of translating
between db errors and "user" errors. The only interface to the db
errors that I could find was the error messages returned from
pg_last_error. Yes, I could have used an array translating between the
the strings returned by pg_last_error or whatever, but *gag* it would
not only have made the code look horrible but would also have been
susceptible to changes in the error messages returned by the db
interface. In the end I changed tack slightly and used pg_send_* and
pg_result_error_field to get a short code I could use as a reference
into an array.