Thank you Michael. I was hoping to do it the native sqlalchemy way, because
my function takes an sqlalchemy-based predicate that needs to be used in
this and another query, so I was hoping to be able to do things natively
using pure sqlalchemy constructs in order to share this predicate.
we just had nearly the identical problem here where we hit the bizarre
fact that LIMIT won't work in the correlated subquery, and we went with
a temp table.
On 11/07/2015 02:27 PM, vitaly numenta wrote:
> Thank you Michael. I was hoping to do it the native sqlalchemy way,
> because my function
