Thanks for looking into this. If it helps you any, this isn't an urgent
problem for me.
It isn't production code that is having this problem, and as you
mentioned I do have
an adequate workaround.
Michael Bayer wrote:
> refresh() isnt doing things the same as expire() does. which is not
> neces
refresh() isnt doing things the same as expire() does. which is not
necessarily wrong, but if you use expire() for now, you'll get better
results. or turn off the lazy=False. but yes its a bug.
David Gardner wrote:
>
> By "simple" I mean it isn't based on my schema, and reproducable :)
>
> Mi
By "simple" I mean it isn't based on my schema, and reproducable :)
Michael Bayer wrote:
> four levels of inheritance ?! hardly simple. turn off the lazy=False for
> now, its an eager loading issue.
>
>
--
David Gardner
Pipeline Tools Programmer
Jim Henson Creature Shop
dgard...@creaturesh
David Gardner wrote:
>
> I was able to reproduce this issue in a simple test using sqlite,
> submitted as a bug
> http://www.sqlalchemy.org/trac/ticket/1485
four levels of inheritance ?! hardly simple. turn off the lazy=False for
now, its an eager loading issue.
--~--~-~--~~---
I was able to reproduce this issue in a simple test using sqlite,
submitted as a bug
http://www.sqlalchemy.org/trac/ticket/1485
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this gr
Forgot to mention this is SQLAlchemy 0.5.5
David Gardner wrote:
> I just ran across something I believe maybe a bug in session.refresh()
> dealing with adjacency lists.
> The situation is after a session.refresh() on a node (in my case a
> 'job'), the children and grandchildren
> have some of t
