sure, but how is your system designed to handle the case where an unintended exception (such as out of memory) is thrown while an exception is being handled?
The situation CAN happen; therefore, there should be some thought put into how the system should respond if it does happen. How should the system unwind and clean itself up? How should client code be informed of the problem? I'm thinking once I get a better understanding of how your exception system works and what its needs are, I will seek to redesign it in such a way that exception handling code never throws except for converting to an intended exception. Perhaps a good approach is to preallocate appropriate exception classes before they are needed in anticipation of them being used. On Apr 23, 2010, at 10:49 AM, Thomas Mueller wrote: > Hi, > > If the system runs out of memory, probably the best action the > database can do is close the database files immediately. > > Regards, > Thomas > > -- > You received this message because you are subscribed to the Google Groups "H2 > Database" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
