OrientDB Schema Options: Schema-less, Schema-full, and Schema-Mixed
I’ve seen a similar approach on handling different schema approaches in the Java Content Repository spec:
Although OrientDB can work in Schema-less mode sometime you need to enforce your data model using a schema. OrientDB supports schema-full or schema-mixed solutions where the second one means to set such constraints only for certain fields and leave the user to add custom fields to the records.
Just in case you aren’t familiar with OrientDB:
