Mark Sapiro writes:
> On 4/2/20 1:05 PM, brian_carpen...@emwd.com wrote:
> > https://mariadb.com/kb/en/why-is-order-by-in-a-from-subquery-ignored/
> > is saying it is not a bug so I doubt SQLAlchemy will think it is.
>
> My take is a bit different. MariaDB is saying this is not a MariaDB
On 4/2/20 1:05 PM, brian_carpen...@emwd.com wrote:
> https://mariadb.com/kb/en/why-is-order-by-in-a-from-subquery-ignored/ is
> saying it is not a bug so I doubt SQLAlchemy will think it is.
My take is a bit different. MariaDB is saying this is not a MariaDB bug.
They would say that it is a
https://mariadb.com/kb/en/why-is-order-by-in-a-from-subquery-ignored/ is saying
it is not a bug so I doubt SQLAlchemy will think it is. We just switched over
to PostgreSQL with very little problem so it is no longer an issue.
Stay healthy Steve!
Brian
Brian Carpenter writes:
> However is there anything you guys can do to mitigate that issue
> with Mariadb?
Bottom line up front: In the meantime I'd say if you want to use
MariaDB you're going to have to sort the results yourself on the
client side. Sorry about that.
Goran's analysis is
Goran Terzic writes:
> Thank you everyone for looking into this.
>
> Looks like the problem is that SQLAlchemy is generating query with
> 'order by' part inside nested subquery, which is not supported by
> mariadb.
Thank you for finding that, I never would have!
>
