Michael J. Sullivan
Michael J. Sullivan
Otherwise we'll probably end up always missing some. If we do it via reflection, it's easy to include extension configs too. This should get all the config properties that can...
Currently we can only configure the instance. See https://github.com/edgedb/edgedb/issues/4672 for a situation where we wanted to configure the database
So instead of ``` default::Movie {title: 'Captain America: Civil War'} ``` we would just display ``` Movie {title: 'Captain America: Civil War'} ``` This will almost always just mean dropping...
If we create a multi property with an exclusive constraint and then make it single, we aren't able to drop the constraint, property, or type anymore: ``` _localdev:main> create type...
Currently, if a type has children and has a multi pointer with an exclusive constraint, updating the pointer to the value it already has will produce a ConstraintError. This is...
It would be limited to object types that have no incoming links, and could be implemented using postgres TRUNCATE
If you have a schema like ``` abstract type X1 { x1: str; y := .x1; constraint exclusive on (.y); }; type X2 extending X1; type X3 extending X2; type...
5.0b3 shipped with an incremented catalog version and so can't be upgraded in place from b1 or b2. It failed https://github.com/edgedb/edgedb/actions/runs/8628182000/job/23650142011, but those don't block the release and were ignored.
We dump basically every fact about the IR when we dump it. Possibly the dumping mechanism should have some notion of verbosity levels, and our AST should be able to...
It might be useful to have a variant of `:=` for inside `update ... set` to mean "set if not empty". Elvis suggested `?:=` on discord. So `set { foo...