Hi Michael,
Thanks for the speedy reply!
That makes sense.
Ok - so in this case, how would we actually get sqlalchemy to return N
distinct 'content' items, rather than N content-plus-joined-table sets?
All the results have full primary keys, so its more likely they are being
de-duped.
Than
On 06/07/2016 03:34 AM, Damian Dimmich wrote:
Hi,
We've been staring at a problem for some time, where an sqlalchemy
generated query we run returns less objects when run with .all() than
the number given to us with a .count().
The same, generated query which we get in our logs/from print(quer
Hi,
We've been staring at a problem for some time, where an sqlalchemy
generated query we run returns less objects when run with .all() than
the number given to us with a .count().
The same, generated query which we get in our logs/from print(query)
returns the same number of rows as the count()