We already have btree and hash indicies but the hash index route for mutli column indices is not ideal to enfore the uniqueness invariant in a convenient way.
This would also be immensily usefull for procedural view primary keys because you could actually determine a pk for a subset of your data :>
Requested by @kistz via the SpacetimeDB site.
I think this would be a great feature. I assume this means I could removed all my redundant ID columns and use a combination of columns instead for a unique primary key. If this is the case, I'd be able to reduce the size of almost all my tables. A very nice win.