That's more of a function specific to your application. SQLA's
attribute events are specifically so you can squeeze in the middle of
its own instrumentation.
On Oct 3, 6:09 pm, Brett <[EMAIL PROTECTED]> wrote:
> I was trying to send events to listeners when attributes changed on my
> model. It
I was trying to send events to listeners when attributes changed on my
model. It didn't really work out that well for me anyways as I wanted
to listen to specific instances and not every instance of a mapped
class.
On Oct 1, 2:15 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Oct 1, 2008, at
On Oct 1, 2008, at 3:28 PM, Brett wrote:
>
> I'm using AttributeExtension for my project and it would greatly
> simplify things if I could receive the events after the attributes are
> set. Is there any way this will make it into SqlAlchemy?
having the events received before is a strong featur
I'm using AttributeExtension for my project and it would greatly
simplify things if I could receive the events after the attributes are
set. Is there any way this will make it into SqlAlchemy?
On Sep 28, 8:09 pm, Mike Bernson <[EMAIL PROTECTED]> wrote:
> Michael Bayer wrote:
>
> > On Sep 28, 200
Michael Bayer wrote:
>
> On Sep 28, 2008, at 8:23 PM, Mike Bernson wrote:
>
>> The set method has changed from 0.5b3 to 0.5rc1.
>>
>> The old set method set the value before it called the set method
>> in attribute extension. The new method set the value after the
>> set method is called.
>>
>
On Sep 28, 2008, at 8:23 PM, Mike Bernson wrote:
>
> The set method has changed from 0.5b3 to 0.5rc1.
>
> The old set method set the value before it called the set method
> in attribute extension. The new method set the value after the
> set method is called.
>
> This is cause me problems becaus
