Uwe Grauer wrote:
> Paul McNett wrote:
>> Thanks again for working on this, and also to Carl, John, and Uwe for 
>> contributing to the discussion. I still think we should keep the 'flag 
>> for delete' up for debate, but exposing transactions to the biz layer 
>> gets me through my immediate need, and probably also makes dabo more 
>> flexible for other needs in the future as well.
>>
>> I'll be extremely comfortable with this and the various bugfixes I've 
>> committed over the past couple months, after the app has been in the 
>> field for a few weeks and subjected to user testing. The last release 
>> was back in November, and much has changed both in Dabo and the app 
>> since then.
> 
> How do you handle Database Exceptions in your new toy? ;-)
> Did you think about it?

I'm not sure I follow the question. If an exception occurs in the data 
layer that I'm not expecting, it won't be handled and so my 
sys.excepthook will handle it by logging the error, emailing it to me if 
possible, notifying the user with a friendly apologetic error message, 
and exiting the app, with no changes made to the database since the last 
save()/commit().

Can you think of a better way to bail out when something unexpected happens?

Paul


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]

Reply via email to