According to the documentation, to operate in strict schema mode you need to set the "mandatory" option to a field which should force the presence of the field. While the "not null" should force having a value in the field. But the database does not behave exactly like that. Instead, If I set mandatory, not only the field presence is forced but I am also forced to input a value.
Second, if I add a mandatory field after objects has been created, the fields does not get added to the old objects, I need to enter each of them to add the new field. While If I delete a mandatory property / field from the schema, all object that had that field remain into the object. So I need to manually delete the field in each object. Is there a way to work in true full schema mode where adding and removing properties/field from a class will modify all the objects in the database matching the same class. I imagine that it could be done with a query, but it should be logical that the "Strict Schema Mode" is actually a "Mode" activated with some option or parameter to make the DB behave differently. -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
