Jack Fischer

Another report here, https://discord.com/channels/841451783728529451/849377751370432573/1162496692822745241 > For anybody else looking at this, the issue was that some long running queries were deadlocking with the migration while trying to modify postgres views

This affects the UI as well as the CLI.

Another simpler example of the implicit limit being applied on an inner query instead of the final output result (possibly comparable to the `with nums := Test.nums` example above) ```...

Also confirmed on 4.x (EdgeDB 4.2+833dd8d (repl 4.0.2+500be79))

Unfortunately no log lines other than the usual (`Connection established to backend database` `Backend connections to database` `Connection discarded` `introspecting database`)

The big item is that this isn't a computed property at all. Just realized this is must just be how inserts are implemented, but suffice to say users don't think...

Perhaps it's coming up as computed because of the `datetime_current` function. However, it's also confusing to call it a "modification". The original query we noticed this in was an upsert...

Another way this crops up: forgetting to not define a shape after turning a select into a with, ```edgeql with gpt4users := (select User {preferredFoundationModel: {provider_model_identifier}} filter .preferredFoundationModel.provider_model_identifier like "gpt-4%"...

@scotttrinh I'm putting that TS knowledge to work

Ah, I see what you mean. So null is not not assignable to required JSON.