On 5/21/15 3:56 PM, Russ wrote:
nope. I'd need a complete, self-contained and succinct example I
can run, thanks
Ok, thanks. This is a beefy one so that will be extremely tricky to
extract. I had hoped that the combo of lazy+joined would have been a
clear indicator since they
Yes, 'number' is a column, as you surmised. When I drop that from the path
it works fine. The only remaining problem is/was that this ends up loading
in every field in the child_product table, and this includes a potentially
massive BSON column (and more).
After looking into this, I've now
On 5/21/15 3:25 PM, Russ wrote:
I have a query I am running where sqlalchemy is throwing this exception:
Exception: can't locate strategy for class
'sqlalchemy.orm.properties.ColumnProperty' (('lazy', 'joined'),)
What causes this is the addition of this joinedload_all option to a
query
I have a query I am running where sqlalchemy is throwing this exception:
Exception: can't locate strategy for class
'sqlalchemy.orm.properties.ColumnProperty' (('lazy', 'joined'),)
What causes this is the addition of this joinedload_all option to a query
(q):
q =
nope. I'd need a complete, self-contained and succinct example I can run,
thanks
Ok, thanks. This is a beefy one so that will be extremely tricky to
extract. I had hoped that the combo of lazy+joined would have been a clear
indicator since they are opposite loading strategies.
Digging
