[Maypole] Dying a good death

[Jesse Sheidlower]

Twice recently I've had experiences were some error in a Maypole
application has caused an improperly large set of results to be
displayed. I was wondering if anyone else might have seen this,
or what a good solution could be.

An example was going to http://mysite.com/myDB/mytable/list ,
when there was an error in a dependency (a required module
hadn't been upgraded properly). I got the error message in my
Apache logs, but Maypole skipped the authentication step,
and skipped the pager, returning the full result set at once.
The navbar also displayed with _all_ tables, not just the
display tables, making my sessions table visible, for example.

Needless to say, if there's an error like this I'd prefer to
display an error page, or at least have the application die
utterly with an Internal Server Error, rather than spewing
out my entire database and all the tables to any unauthenticated
user.

Anyone else see anything like this?

Jesse Sheidlower