My Notes
- Programmatic migration convenience functions in language bindings
- https://discord.com/channels/841451783728529451/849377751370432573/1108000961449963520
- https://github.com/edgedb/edgedb-cli/issues/1046
- Elvis: implement as an entrypoint in the binding, not in the client
- Multiple concurrent editors of schema?
- Create database, role, and set password in bootstrap command
- Multiple macOS notifications when using a new EdgeDB version
- https://edgedb.slack.com/archives/CNECHA9EW/p1684523346812119
- Open a ticket in CLI repo
Meeting Notes
Under the hood, a
multilink is stored in an intermediate association table, whereas asinglelink is stored as a column in the object type where it is declared. As a result, single links are marginally more efficient. Generallysinglelinks are recommended when modeling 1:N relations.
For most users, it wouldn’t matter. Only an optimization when queries are slow.
Last sentence: reverse the link to the other end and use a computed backlink. If you need to mutate, you would also have to mutate from the other side if you switch the direction of the link to change a multi to a single.
Put it in a separate section about schema and performance.
- How to use analyze
- How to use indexes