I had the same problem, I'm not sure about your code, but for me, the
source of the problem was that I tried to merge two different objects that
had the same primary key, so the merge supposedly worked, but when I
commited, I got the same error you did.
Tp solve it I just kept the items I
.
Thanks,
- Yaniv
On Monday, December 17, 2012 7:50:02 PM UTC+2, Michael Bayer wrote:
On Dec 17, 2012, at 12:35 PM, ya...@aknin.name javascript: wrote:
Hi,
SQLAlchemy populates an instance's __dict__ with lazily related instances
when the attributes for these instances are first accessed
for solutions that rely on the 0.8 introspection API, but
will be even more interested in solutions that will work in 0.7.x.
Thanks again,
- Yaniv
On Monday, December 17, 2012 7:50:02 PM UTC+2, Michael Bayer wrote:
On Dec 17, 2012, at 12:35 PM, ya...@aknin.name javascript: wrote:
Hi
to all relations in any instance's
__dict__. These proxies can be transparently replaced with the real thing
upon first access(if the list will agree with this approach, I'm willing to
try my hand at producing a patch).
What do you think?
- Yaniv
--
You received this message because you
