Użytkownik Ed Leafe napisał: > There really shouldn't be one single SqlManger object. The recent > issues with the M-M cursors showed that flaw. The original design had each > cursor be its own manager, with the bizobj handling coordinating the various > cursor's properties; I think something like that would be much more robust. >
AFAIR latest problem resulting duplicating cursors in MM and common dBizobj pool, so I can't see SqlManager correlation. 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. -- Regards Jacek Kałucki _______________________________________________ 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]
