On Dec 6, 2011, at 2:26 AM, Jacek Kałucki wrote:
> AFAIR latest problem resulting duplicating cursors in MM and common dBizobj
> pool, so I can't see SqlManager correlation.
When the MM cursors had their properties set, it overrode the original
bizobj settings for their "normal" cursors. IOW, all cursors related to that
bizobj now had the MM data, not just the ones that were added to handle those
relations.
> Original design has some implementation aspects using SqlManager
> (dCursorMixin.sqlManager) and cursor properties synchronized on demand.
> My question is why we made them redundant if they *must* be synchronized
> across all cursors except the AuxCursor? Why not to have one SqlManager to
> rule them all ;-) ?
> It's a waste of memory and CPU time IMHO. But I don't insist.
If they all had identical purposes, you could have a single manager
instance. But that's not the case. Also, there are more properties that are
synced than just those related to the sqlManager; the sqlManager can be ignored
completely if the user manages their own SQL code.
-- Ed Leafe
_______________________________________________
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]
