Ed Leafe wrote: > On Jan 14, 2009, at 2:55 PM, Paul McNett wrote: > >> Consider this experimental. Because it is set on a backend object >> and not >> a cursor, it doesn't make sense to expose the property in >> dCursorMixin. > > Backend objects are merely the variable parts of dCursorMixin for > different backends. IOW, things go in dCursorMixin unless they are > done differently with one of the supported databases. In that case, > the dCursorMixin code is changed to pass the request through to > self.BackendObject, and dBackendObject adds the method with the most > common implementation, or a stub if it differs in each. Then the > backends that handle it differently override the behavior in their > subclasses.
dBackend also holds the actual db connection (in the _connection attribute) from which all cursors are generated. > Code should *never* even know about a specific implementation detail > like this. dBackend is all about specific implementation details. KeepAliveInterval, when/if made more available to public use, would exist at a higher level than dBackend. However, I don't believe it would be at the dCursorMixin or dBizobj level, because one connection could be supporting many dCursorMixin objects. It probably belongs in dConnection, with the property exposed with the other connection parameters. 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]
