On May 20, 2009, at 11:04 AM, Paul McNett wrote:
>> How would you handle existing code that may reference the constants?
>
> What user code would reference the constants, do you think? User
> code could reference
> the *ChildLogic attributes of the bizobj instance, which we could
> handle gracefully
> with a deprecation warning.
I meant that if someone had code that sets the logic, they would have
something like either:
self.deleteChildLogic = dabo.dConstants.REFINTEG_RESTRICT
-or-
self.deleteChildLogic = 2
They wouldn't have anything that would set these to a string value,
which is what you're proposing. We could handle them in the setter of
the new property, but anything that referenced these values would break.
> The other thing that could be good is allowing for different logic
> for different
> child tables, perhaps by adding *ParentLogic props that override
> whatever the parent
> has as *ChildLogic.
That may be useful, but is a separate discussion.
-- 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]
