Posted by Jerry Stuckle on 11/28/07 18:37

Knut Krueger wrote:
> Jerry Stuckle schrieb:
>> In general, it's also a bad idea to have error_display enabled in a
>> production system. It can show other things about your system when
>> there are problems - things you don't necessarily want known (i.e.
>> contents of SQL statements). But it's necessary for development.
> yes it depends in my files on then content of $testmode TRUE/FALSE in a
> config file and will be submitted with session variable or post forms
> otherwise I am using the PHP default (think it is set to #40)
>
>
>>> But this error is included in the proof function from those selected
>>> data before updating the data.
>>>
>>
>> ??? I don't understand this part.
>>
>
> But this error *handling* is included in the proof function from those
> selected data before updating the data.
>
> select -> update
>
>
> Knut
>

But if the error occurs once every 10 years because a user incorrectly
deleted a required table with PhPMyAdmin, that's their problem. I'd let
the message go ahead and be displayed.

I don't try to protect against user stupidity like that.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]