Documentation for AttributeImpl.callable_ still reads
optional function which generates a callable based on a parent
instance, which produces the default values for a scalar or
collection attribute when it's first accessed, if not present
already.
But it seems it
On Dec 26, 2011, at 9:07 AM, Kent wrote:
Documentation for AttributeImpl.callable_ still reads
optional function which generates a callable based on a parent
instance, which produces the default values for a scalar or
collection attribute when it's first accessed, if
yes a few change names, reconstruct_instance, init_instance, init_failed.
On Dec 24, 2011, at 7:42 PM, Kent Bower wrote:
Right. And reconstruct_instance() was renamed load()?
On 12/24/2011 5:56 PM, Michael Bayer wrote:
On Dec 24, 2011, at 10:04 AM, Kent wrote:
As the migration guide
As the migration guide suggests, I'd like to embrace the events API.
Is mapper event load() invoked at exactly the same place as the
deprecated reconstruct_instance() ?
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send
On Dec 24, 2011, at 10:04 AM, Kent wrote:
As the migration guide suggests, I'd like to embrace the events API.
Is mapper event load() invoked at exactly the same place as the
deprecated reconstruct_instance() ?
yeah nothing has been moved. All the places where the internals would call
Right. And reconstruct_instance() was renamed load()?
On 12/24/2011 5:56 PM, Michael Bayer wrote:
On Dec 24, 2011, at 10:04 AM, Kent wrote:
As the migration guide suggests, I'd like to embrace the events API.
Is mapper event load() invoked at exactly the same place as the
deprecated
