Yep, current trunk works ok. Any chance of getting a 0.4 backport of the fix? I'm stuck on 0.4 for the next couple of months.
On Sat, Apr 4, 2009 at 4:44 PM, Michael Bayer <mike...@zzzcomputing.com>wrote: > I think this may have been fixed in 0.5.3 or trunk, see if you see a diff. > > On Apr 4, 2009, at 3:01 PM, Rick Morrison wrote: > > I'm running into this one now as well, though it's with Session.expire(), > not Session.merge(). > The attached script will reproduce the issue against the 0.4 trunk > > > > > On Mon, Dec 1, 2008 at 11:05 AM, Michael Bayer > <mike...@zzzcomputing.com>wrote: > >> >> this could be a bug, depending on if we have test coverage for >> session.merge() in conjunction with "dynamic" relations. can you >> reproduce this against the latest 0.5.0rc4 or 0.4.8 release, and if so >> can you make a short test case ? >> >> >> On Dec 1, 2008, at 6:43 AM, Nabla wrote: >> >> > >> > Hi, >> > can anybody please check this: >> > I have some script using SA and somewhere in the script I call >> > sess.merge(obj) and got this error: >> > >> > 'DynamicAttributeImpl' object has no attribute 'accepts_scalar_loader' >> > >> > I don't understand fully what 'accepts_scalar_loader' is, but, I tried >> > to add this to attributes.py: >> > >> > class AttributeImpl(object): >> > """internal implementation for instrumented attributes.""" >> > >> > accepts_scalar_loader = True >> > >> > ... >> > And it works I hope. >> > I don't know if this is my misunderstanding something or SA bug? >> > > >> >> >> > > > > <expire_bug.py> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
