What external logic? You mean having to bind the logic for graph multiplicity and direction in your own code? I can agree with that. That would be ridiculous and why we ended up finding ODB too! We don't want to have to think about all that in detail.
However, in this thread, we are talking about abstracting operations *within* the database to end up with more logical language constructs, so the ODB SQL+ is more declarative and concise, when building edge relationships and their direction. I still can't figure out how to do multiplicities of MANY2ONE and ONE2MANY with IN, OUT and UNIQUE constraints. That might be because, I just turned on light weight edges and am going bonkers with Studio trying to create edges that show up properly in the graph view with the right relationships. LOL! But, that is probably just me and my lack of knowledge. Though, if the change to heavy weight edges by default in 2.0.X was a matter of simplicity of use, I can now fully understand why light weight edges are now off by default. Using heavy weight edges seems so much easier. :-) I think I'll change back to heavy weight edges and see if I can do the MANY2ONE and ONE2MANY with IN, OUT and UNIQUE constraints. 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.
