darwino / diana-driver Goto Github PK

An HTTP implementation could either use the Darwino remote classes or REST services directly.

See https://github.com/eclipse/jnosql-artemis-extension/tree/master/couchbase-extension

Currently, they wrap all such exceptions in RuntimeException in order to more-closely match the original Couchbase code. This is probably not beneficial, though.

Currently, the driver uses the first database name from the app manifest. This would be better to have as a configuration option.

It wouldn’t be hard to implement a driver to use Darwino like a key/value store. A graph variant would be more work, but also more useful, and still doable.

Currently, entity names are mapped to the "form" field, Domino-style, with most things expecting that documents will be kept in the default store. It may make more conceptual sense to change that to be the store ID, though that would add programmer overhead in defining stores for each model object in the DB manifest.

Perhaps it would be best to have an alternate driver implementation that does this.

A method could be tagged with @Cursor, and the collection manager could look for @Param arguments to pass as params to the final cursor.