What is the best or recommended way to set up a master/ child relationship between two classes/ vertices, where if one master vertex is deleted, all linked children would also be automatically deleted? Must this be done at application level or is there a feature in ODB to allow this type of relationship?
If there were millions of users in the database and a class is using oRestricted, would there be millions of user ids stored in the _allow* fields for a single record, if all the millions of users should be allowed to view that record? If I understand roles properly, there isn't a way to share data between roles. The role feature is more for CRUD control than data visibility. For instance, say we have a role hierarchy as follows, with roles A, B, C, D, E and F: A | | C E | | D F I'd like to have users in role A be able to see all records from users with roles C, D, E and F. Users with role C can see data from users with role D, but not from users with roles E and F. The same goes with users with the role E. They can see data from the users with role F, but not from users with roles C and D. Is there a way to model this with ODB? If not, is there a recommended way? Scott -- --- 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.
