DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4032>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4032 Bad DB structure causes store problems [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From [EMAIL PROTECTED] 2002-12-30 01:18 ------- One solution is during the repository initialization, check the database table with DatabaseMetadata for the appropriate structure of the table we need, and if it doesn't match, then fail. If DatabaseMetaData isn't supported (throws exceptions), then just skip the check. I prefer this as if the check isn't possible (for database restrictions or driver problems or whatever), we can just skip the check and there is no foul. Another possible solution is to try some non-functioning SQL to insert/select the datasets, and if that fails, then fail. This opens the door for most bad-side effects though, so I'd rather not do this. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
