Jeff Davis wrote:
> On Wed, 2007-05-30 at 12:18 -0600, Scott Ribe wrote:
>>> I thought it had to do with letting a form sit around too long and
>>> then /. timing out the state.
>>>
>>> That's probably not good anyway: it should at least give you a real
>>> error message. However, they might not consider that a bug.
>> I didn't let the form sit around at all--didn't think to mention that
>> before. It may well not be related to MySQL at all, the point is simply that
>> although /. is well-known, gets a lot of hits, and works well enough for its
>> intended purpose, it is buggy and is NOT an example of what would be
>> acceptable reliability for most "mission critical" applications.
>>
>
> I was agreeing with you.
>
> I think that's what the "invalid form key" error is supposed to mean,
> but it probably happens for all kinds of other cases, too (which is bad
> and causes confusion).
>
> I agree that /. not a great example of stability or correctness.
Interesting statement. Question: What would be a great example of
stability of correctness?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
