Mordechai Meisels
Mordechai Meisels
Some time has passed, and I changed my view (pun intended) on managing views in orchid. Instead of writing a migration with `createView()` I'm using raw SQL in the migrations/recurrent...
I could just use `as number`, but the get could also be part of a subquery.
> It's caused by mutability I'm not entirely sure what you mean, but there is indeed a JavaScript level condition which adds another `where` to the query (using `q` variable...
What I mean was that while i simplified my code in this issue, it really looks something along the lines of this: ```ts let q = db.facility.select({ integrations: q =>...
Ok, done. Will keep you posted
The error happened again, no log with the text "suspicious join" in the logs at all.
I'm still at 1.42.1 and can't upgrade due to breaking changes and unresolved bugs.
Currently, my view lives in a recurrent migration BTW.
Until now I've queried the view through a computed field in the parent table, using raw SQL with `row_to_json` to get the same result as an ORM relation. But, as...
I figured a workaround, via `withSql` I can pull the view into a CTE and then select through joining it to the main query. But I found it not to...