I am using mysql.
I have a calss created using REflection
LinkVote
I just noticed that in the latest version of the branch, there's a
new_instance() call that is using a class' __new__ method in order to
create a new instance, rather than using 'class()'. What I'd like to
find out is how to get around this, because Trellis objects will not
be properly
Phillip J. Eby wrote:
I just noticed that in the latest version of the branch, there's a
new_instance() call that is using a class' __new__ method in order to
create a new instance, rather than using 'class()'. What I'd like to
find out is how to get around this, because Trellis objects
On Mar 27, 2008, at 2:51 PM, Phillip J. Eby wrote:
I just noticed that in the latest version of the branch, there's a
new_instance() call that is using a class' __new__ method in order to
create a new instance, rather than using 'class()'. What I'd like to
find out is how to get around
On Mar 27, 2008, at 3:11 PM, Michael Bayer wrote:
also, rev4361 has broken some tests.
rev 4362 fixes that particular issue. I know that the sweep
function there is sensitive in other cases, such as ticket #882, where
if not done properly it can also trip up zope.interface...so it
Phillip J. Eby wrote:
At 12:02 PM 3/27/2008 -0700, jason kirtland wrote:
Phillip J. Eby wrote:
I just noticed that in the latest version of the branch, there's a
new_instance() call that is using a class' __new__ method in order to
create a new instance, rather than using 'class()'. What
At 02:26 PM 3/27/2008 -0700, jason kirtland wrote:
new_instance creates an instance without invoking __init__. The ORM
uses it to recreate instances when loading from the database.
new_instance can be added to InstrumentationManager as an extension
method... The ORM doesn't care how
Thanks Jason! It was nice meeting you at Pycon.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send
