[Zope-DB] How to do analysis? (was Re: Saga continues...)
Bo M. Maryniuck
b.maryniuk at forbis.lt
Fri Oct 3 11:23:33 EDT 2003
On Friday 03 October 2003 15:42, Matthew T. Kromer wrote:
> As Bo said, this kind of object is best instantiated at the
> module level and NOT as a persistant or thread-specific Zope object.
> There are a lot of gotchas with doing this, since objects that exist
> "outside" of Zope still need to do the right thing w.r.t. Zope
> transactions if they are used within the context of a transaction.
Yes. But my DA a bit simpler: single user per single Zope session per single
Oracle session. To get this, I use lock's. This means, that you can not get
the same uncommitted connection untill it is committed or aborted. This works
exactly as Oracle Forms does: untill you save and commit the transaction (or
reject/abort) you will not be able to do something else.
Well, not that multitasking :-) but at least works as stable as a rock. Maybe
I still something missed yet. If yes, would be very nice to get it know...
Prediction is very difficult, especially of the future.
-- Niels Bohr
More information about the Zope-DB