Jack Fischer

I wonder if there is a correctness issue right now; the only way to write `null` for a JSON field is to have it be `optional` in the query, and...

Really appreciate the openness with all the thinking

I also get a warning thrown on macos after CLI upgrades. I don't look closely at it but it is essentially saying the binary has changed. Will capture details next...

This seems like correct behavior. Maybe you'd want the error message in the UI instead of `Failed to fetch data`

Data is broken at the schema level though - wouldn't you receive the same error making an equivalent query in the CLI?

Little weird that it does `RESET EXPRESSION;` twice but that probably doesn't matter.

Similar to https://github.com/edgedb/edgedb/issues/6477. In this case maybe the intended operation should be allowed though.