rfcs
rfcs copied to clipboard
edgedb
RFCs for major changes to EdgeDB
Provide a way to specify ordering for the index expressions. Also make the support of indexes on multiple fields more consistent (stop using tuples for that).
One might say that this is not big enough change for a RFC, but hey let me have my fun. I intentionally didn't push match in RFC title, because this...
Add a way to define a fallback mechanism for indexes based on extensions being enabled or disabled.
Add a mechanism for grouping access policies together to enable code re-use and clearer semantics.
Add the concept of `access group` in addition to `access policy` as a way to address code duplication and boilerplate.
| Code Name | RFC | Champion | Possible Release | Description | |---|---|---|---|---| | Ports (edgedb/edgedb#1910) | Tomorrow | @1st1 | `v1.0` | Connection pooling, configuration of extra ports,...
This adds to RFC 1001 at #4 # Overview Features supported by HTTP: 1. `Authorization` header 2. `Cookie` 3. Basic and digest auth by browser (unusable) Features suported by browser-based...
# Motivation Each revision is a file in `dbschema/migrations/*` per spec. Files are stored in revision control, so technically can be edited after being registered in the database server. Even...