On 5/24/07, George Frink <[EMAIL PROTECTED]> wrote:
Hello:
Thank you again for the help, Dave.
All is now well.
Just in case someone might benefit from them, a summary of the
solutions follows.
I'm glad you were able to figure that out. Thanks for writing up your solution.
(2) Restoring the contents of the "folderassoc" table to its state
at the time of still-unexplained deletion.
That deletion is pretty frightening. Nobody else has reported that
problem, so I hope it is a one-time fluke or user-error on your part.
Any ideas how it could have happened?
In retrospect, I should have devoted more time to reading and
enjoying the source code which emitted the two errors which
confounded me.
Had I done so as my first recourse, I would have understood each
error and its associated stack trace as a meaningful error message.
No excuse.
It does occur to me, and perhaps I am being unreasonable here, that
those who have not been programming in Java for a few years might
perhaps benefit from error messages which are somewhat more
expressive in a literary sense.
Better error messages would definitely be helpful everywhere in
Roller. Users should never have to resort to reading the source code.
But database corruption is non a common event with Roller (or at least
with post 1.x Roller), they're hard to recover from and hard to
explain via error messages.
One reasonable rejoinder would be that if I feel strongly enough to
voice that sentiment in public, I should offer code (which would be
accepted or discarded as appropriate). Not talk. Point taken (falls
silent ... turns to keyboard).
Specific suggestions for improving error messages would also be helpful.
- Dave
