You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In sqlite at least (and I'd expect other dbs as well) you can have any number of CTEs in the with query, per https://sqlite.org/lang_with.html . Especially see example 3.5 which has 4 recursive CTEs and one non-recursive CTE (a).
I'm not sure what the impetus for that line was, but would dropping it be reasonable? Are there other parts of the code that rely on it having only one CTE?
The text was updated successfully, but these errors were encountered:
andrewbaxter
pushed a commit
to andrewbaxter/fork-sea-query
that referenced
this issue
Nov 8, 2024
I tested this with sqlite and the queries execute successfully. It's
possible that there are other incorrect behaviors that can be
pre-emptively caught, perhaps those could be added in a new PR later.
Description
Per https://github.com/SeaQL/sea-query/blob/master/src/backend/query_builder.rs#L780 when you do a recursive with you are only allowed to have one CTE.
In sqlite at least (and I'd expect other dbs as well) you can have any number of CTEs in the with query, per https://sqlite.org/lang_with.html . Especially see example 3.5 which has 4 recursive CTEs and one non-recursive CTE (
a
).I'm not sure what the impetus for that line was, but would dropping it be reasonable? Are there other parts of the code that rely on it having only one CTE?
The text was updated successfully, but these errors were encountered: