It shouldn't break your apps. In dBackend, I have it defaulted to use dCursorMixin if the specific backend doesn't override it, which is the original behavior. Are you saying it doesn't do that?

Regards,

Nate

On Oct 14, 2012, at 6:38 AM, Jacek Kałucki <laborm@rz.onet.pl> wrote:

> Użytkownik Nate Lowrie napisał:

>> ===================================================================

>> --- trunk/dabo/biz/dBizobj.py 2012-10-11 19:13:53 UTC (rev 7277)

>> +++ trunk/dabo/biz/dBizobj.py 2012-10-13 18:39:16 UTC (rev 7278)

>> @@ -21,8 +21,6 @@

>>

>> class dBizobj(dObject):

>> """ The middle tier, where the business logic resides."""

>> - # Class to instantiate for the cursor object

>> - dCursorMixinClass = dCursorMixin

>> # Tell dObject that we'll call before and afterInit manually:

>> _call_beforeInit, _call_afterInit, _call_initProperties = False, False, False

>

> Hi.

>

> This change breaks all my applications, since they don't get customized cursor class anymore,

> they get default one from the backend instead.

> Why not simply reference dBizobj.dCursorMixinClass class attribute with your customized

> cursor if you need it?

> You should create dBizobj.getCursorMixinClass() method at last to allow override default cursor

> creation chain behaviour.

> --

> Regards

> Jacek Kałucki

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: Dabo-dev@mail.leafe.com

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/F456EF96-5987-4656-A491-27824A36EAF7@gmail.com