On Sun, Sep 28, 2008 at 06:01:24PM -0400, David Turner wrote:
> I have written a patch for this. Since I noticed the change in the
> inheritance system, that's where the test for it ended up going. If
> this is OK with you, I'll commit it.
Ok from me. It passed the test suite in the trunk.
On Sun, 2008-09-28 at 00:51 +0400, Oleg Broytmann wrote:
> On Sat, Sep 27, 2008 at 01:51:45PM -0400, David Turner wrote:
> > Depending on how attributes are set on child classes, rowupdatesignal
> > fires either just on the base class, or on both the base and the child.
> > This is inconsistent.
>
On Sat, Sep 27, 2008 at 01:51:45PM -0400, David Turner wrote:
> Depending on how attributes are set on child classes, rowupdatesignal
> fires either just on the base class, or on both the base and the child.
> This is inconsistent.
I suspect a subtle bug in SLObject._SO_setValue().
Oleg.
--
Depending on how attributes are set on child classes, rowupdatesignal
fires either just on the base class, or on both the base and the child.
This is inconsistent.
from sqlobject import *
from sqlobject.inheritance import InheritableSQLObject
class Base(InheritableSQLObject):
name = StringCol
