Elvis Pranskevichus

> I think executing the first one is pretty clearly best Yeah, this makes it similar to a Python exception handler.

Currently, you have to specify the output shape explicitly. The main reason is that it is not obvious what is meant by `*`. Is it all properties, or all properties...

The proposed solution is to provide an autocomplete shortcut so that typing `SELECT User{*` would complete to a full list of type properties (but not links).

Yeah, it appears you cannot update the just-inserted tuple. Bummer.

Linking with CLI effectively records the TLS certificate and the _password_ of the remote instance. If you want to connect without linking, you can specify these in the environment (`EDGEDB_PASSWORD`...

You can put the certificate into a file and then specify the path to that file with `EDGEDB_TLS_CA_FILE` (most environment variables support the `_FILE` variant).

We are currently working on JavaScript and Go bindings. Java and .NET will be the next two platforms we will add support for. Meanwhile, you can use the [EdgeQL over...

Right, support for transitive closure (a.k.a recursive CTE in SQL) is something we are planning to implement in EdgeQL soon. See also an earlier discussion in #2634.

Time travel can be emulated with `select` policies as well, e.g: ``` abstract type Temporal { required property validity_period -> range; access policy hide_invalid allow all using ( contains(.validity_period, datetime_of_transaction())...

Looks like a bug to me, unrelated (but somehow uncovered by) the change