> 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.
--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice