You mean when you are actually defining the class, right? Otherwise, what happens when you use ONE2MANY in one statement but not in another?
So maybe something like this CREATE CLASS Belongs EXTENDS E FROM Person TO Tool ONE2MANY I'd definitely like that too. However, considering there are already a number of issues with SQL parsing, I certainly wouldn't push for syntactic sugar. On Saturday, October 31, 2015 at 9:17:05 AM UTC-7, scott molinari wrote: > > Thanks Ziink A. > > But, be honest. Wouldn't a simple > > orientdb> CREATE ONE2MANY EDGE Belongs FROM Person TO Tool > > be easier, where ODB does the "linking" itself and with the right unique > indexing on the right in or out properties? > > 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.
