vasa

We are looking for maintainers. As of now, the project is on standby.

Here is a related issue from the specs repo: https://github.com/dappkit/aviondb-specs/issues/3

Thanks for sharing your views @vaultec81 @deanpress. We can discuss more the issues that @vaultec81 has stated in terms of conflicts. I'll work on a new issue for specs to...

@vaultec81 Should we add the CID of the Schema with the oplog? That way the oplog would stay clean & light.

@vaultec81 About the Protobuf conversion, is that done on `orbit-db-io` level?

> oplog would reference an ID that connects back the Scheme JSON data. @vaultec81 So, where & how should I store the Schema JSON & their respective id(s)? Given that...

Yeah that makes sense. So when we replicate (from peer1 to peer2) the collection, then the Schema will also get replicated with it, right?

> Protobuf serialization wouldn't happen on the orbit-db-io level rather the level where aviondb stores its state. I'm a bit confused here. Where do we store the "state"?

Got it.

In case we add Schema support, should we allow creating a collection without a Schema? IMO: We should not allow collections without a Schema.