Michael J. Sullivan

You can't update objects that you can't select. (In EdgeQL, at least. If you can in our SQL layer that's probably a bug we need to think about.)

I've focused mostly on the compiler component, but there is also a lot of room for cleverness to make this truly in place. With appropriate setup, almost all of this...

Other design notes (will edit): * I think that scalar types in metaschema and the standard library still need to go into global namespaces, so we'll need to be careful...

Remaining TODOs: - [ ] Extension upgrade support (https://github.com/edgedb/edgedb/issues/7724) - [ ] Parallelize upgrade (by using compiler pool)? - [x] Support upgrade while old version is running - [x] Block...

Closing this now. https://github.com/edgedb/edgedb/issues/7724 is still an important follow up, but if necessary it can wait until 7.0.

> The solution here would be to apply the `select` access policy on targets when deleting links. We have a "deleting links" operation, `-=`, and the `select` access policy is...

Hm... let me dig into something a bit more. I had forgotten that we actually copy the annotations onto the indexes themselves... but I can't remember why? Edit: Ah, because...

Here's a query that will generate the exact same JSON I think, from introspecting: ``` WITH ai_objs := ( SELECT schema::ObjectType FILTER 'ext::ai::EmbeddingModel' IN .ancestors.name ) SELECT json_object_pack( FOR obj...

Fixing half-dunder names has the problem that it leaves any database still using them (via an inplace-upgrade or minor version upgrade) in a pretty broken state, where some of the...

Should we merge this?