Tryneus

I've been meaning to revisit the existing metadata management, because it's rather cumbersome, and we should be using changefeeds to have multiple fusion servers coexist on the same database peacefully...

Using a user-defined index like that breaks the assumption that chaining operations on two different fields will have the same behavior as an operation on either field. A query such...

@marshall007 - I don't think we need deterministic key order, rather we need to know the order that the fields go into the index (this is important for matching queries...

@mlucy - the index is only created once, and we save the name in our internal structures we use for matching queries to indexes - we aren't "guessing" the index...

@stellanhaglund - I've actually reworked how endpoints are created in the permissions branch (see PR #331). Adding a request handler is the same, but the endpoint must expose a different...

I may be wrong, but the documentation for most (if not all) auth providers say that you should only use HTTPS for the redirect URI. At least some of them...

@gamesbrainiac - I'm not entirely sure what this issue is proposing. I tried out the existing `asyncio` implementation of the Python driver, and it appears to work correctly with `async`...

@chipotle - currently there is no client support for it, it's just an option available in the protocol.

The current format is each field in the index, concatenated in order, delimited by underscores. Undescores and backslashes in field names are escaped with backslashes. Examples: | index fields |...

Because validators are run on the horizon server, and not on the database, if two clients attempt to write to the same row at the same time, one will have...