Alex Lazar
Alex Lazar
Per the thread, the workaround is to do ``` with users := (select User filter ...) select (users union {}) { name, email, username } ``` to force a set
Sorry, forgot to come back and update this - `multi` is actually the better solution than the union thing. It goes on the final shape rather than the `with` variable....
I've also encountered this: https://github.com/edgedb/edgedb/issues/6668 - `in` is causing it to ignore the index
Thanks for the fast response! I think I like allowing unused with bindings because string building queries gets a lot more annoying if I have to conditional every little thing....
Also worth noting, asserts in a shape where that shape is not then part of the overall select also do not fire. ``` with thing := (select Thing { is_valid...
Further discussion in the discord thread
Also not just empty set, but it fails to do number coercion, eg cannot do `@int32prop := 1`, must do `@int32prop := 1`
Going to guess the answer here is "postgres forces this" but fingers crossed it's an easy fix somewhere
Interesting, thanks I'm also hitting similar issues on even simpler queries where I would expect `exclusive` to kick in. It seems it doesn't handle a lot of cases around computed/multi...