Thanks Michael. As always I appreciate the support here.
I'll try it out. It might actually be faster to redo these two tables in
the model in plain SQLAlchemy than trying to figure out what's wrong with
the current one.
And, uhm, there is no difference between user_account and workers. I
also in 0.8 I'm definitely going to make it so that primaryjoin thing isn't
needed for this kind of case, foreign_keys=foo.id will be enough, see
http://www.sqlalchemy.org/trac/ticket/2411 .
On Feb 18, 2012, at 7:30 AM, Jakob D. wrote:
Thanks Michael. As always I appreciate the support here.
Awesome =)
Your example definitely works.
But given my nature, I cannot leave things like this unanswered. So I took
a few steps back and debugged some more.
I removed a few fields from the model and added them one by one with
elixir. When using reverse I actually had to specify the field on
On Sat, Feb 18, 2012 at 07:57:14PM -0500, Michael Bayer wrote:
I don't know that customizing instrumentationmanager is all you'd need.
There's lots of bookkeeping occurring with instancestate that takes time and
is related to state tracking and persistence. The whole need for
__setstate__ is
On Feb 18, 2012, at 8:05 PM, Andrey Popp wrote:
On Sat, Feb 18, 2012 at 07:57:14PM -0500, Michael Bayer wrote:
I don't know that customizing instrumentationmanager is all you'd need.
There's lots of bookkeeping occurring with instancestate that takes time and
is related to state tracking and
