Hi, the constraint would be in the Vertex's User.outRate property. LINK because OrientDB manages the relationships with LINK or LINKSET for respectively 1 and N cardinality. In your case you can force LINK so you shouldn't have more than 1 edge.
Let me know if works. Lvc@ On 14 April 2014 15:19, Munish Chopra <[email protected]> wrote: > Thanks a lot for quick reply. > > Our edge has a property rating-value, where we store value of the rating. > Can links have properties? > > Can you please provide SQL for that as well? I could't find it in > documentation. > > Regards, > Munish > > -- > > --- > 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. > -- --- 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.
