you need to return EXT_CONTINUE for your TimestampExtension methods.
On Nov 5, 2007, at 4:45 PM, Rick Morrison wrote:
from sqlalchemy import *
from sqlalchemy.orm import *
import datetime
import time
class TimestampExtension(MapperExtension):
def _decorate_instance(self, instance):
Ah. OK, thanks!
I checked in a small update to the 3.x - 4.0 migration guide in the docs to
note this.
On 11/5/07, Michael Bayer [EMAIL PROTECTED] wrote:
you need to return EXT_CONTINUE for your TimestampExtension methods.
Rick
--~--~-~--~~~---~--~~
You
Michael Bayer wrote:
On Jul 30, 2007, at 4:58 PM, Jonathan LaCour wrote:
Michael Bayer wrote:
its a model taken from the way event loops usually work; any consumer
along the event chain is allowed to say, ive consumed the event and
stop further handlers from dealing with it. we can
jason kirtland wrote:
i think a name change is probably in order at the very least.
r3130 in the trunk implements a name change- EXT_CONTINUE will
propagate the hook to the next extension or back to the base
implementation. EXT_STOP will halt propagation.
it's only a name and doc change:
On Jul 30, 2007, at 4:58 PM, Jonathan LaCour wrote:
Michael Bayer wrote:
its a model taken from the way event loops usually work; any consumer
along the event chain is allowed to say, ive consumed the event and
stop further handlers from dealing with it. we can certainly change
the names
Michael Bayer wrote:
both of your before_update() functions return EXT_PASS. theyll both be
called.
Well, yeah. I just found it a little bit odd that I had to do this.
When I saw EXT_PASS, I didn't think it meant continue along with other
mapper extensions. It seems like a bad idea for one
On Jul 30, 2007, at 3:41 PM, Jonathan LaCour wrote:
Michael Bayer wrote:
both of your before_update() functions return EXT_PASS. theyll
both be
called.
Well, yeah. I just found it a little bit odd that I had to do this.
When I saw EXT_PASS, I didn't think it meant continue along
Michael Bayer wrote:
its a model taken from the way event loops usually work; any consumer
along the event chain is allowed to say, ive consumed the event and
stop further handlers from dealing with it. we can certainly change
the names around into something less ridiculous. unfortuantely,
