On Friday 22 June 2007 11:15, Paul McNett wrote:
> Ed Leafe wrote:
> > Changed:
> > U trunk/dabo/biz/dBizobj.py
> >
> > Log:
> > Handled the NoRecordsException in the bizobj without aborting the
> > process. The exception is still passed up to the calling layer so that
> > the caller (usually the UI) is aware that there are no records, and can
> > respond appropriately.
> >
> >
> > + except dException.NoRecordsException:
> > + # No need to abort the transaction because of this, but
> > + # we still need to pass the exception to the UI
> > + uiException = dException.NoRecordsException
>
> If you would have written it like this instead:
>
> except dException.NoRecordsException, e:
> uiException = e
>
> Then the original exception would be propagated up to the ui layer,
> instead of a brand-new one with no context in the traceback.
>
> But that may not be a good idea for reasons I haven't considered.
In dForm
except dException.dException, e:
dabo.errorLog.write(_("Requery failed with response:
%s") % str(e))
self.notifyUser(str(e), title=_("Requery Not Allowed"),
severe=True)
So in my case the exception is handled at the Form level.
You are setting the exception at the bizobj level. So if I do
bizobj.requery()
will the children be set correctly???
--
John Fabiani
_______________________________________________
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/dabo-dev/[EMAIL PROTECTED]
