Hello Curtis, I had the same frustration (as you can see in this thread <https://groups.google.com/d/msg/orient-database/56yA8Rz-8pk/t5VYv3wqaM8J>).
I didn't really get the message across, so I hope your mentioning it again will help the developers understand that some kind of 'join' syntax would be useful: for exploring the database, and creating new, previously inexistent edges based on various properties from different vertices. I don't think there is a solution yet for what you want to do, but I do hope something ike that will be added soon to the SQL syntax. Op donderdag 21 augustus 2014 20:00:58 UTC+2 schreef Curtis Mosters: > > I just did it with: > > CREATE LINK out_hasAppln TYPE linkset FROM person.id To post.id > CREATE LINK in_hasAppln TYPE linkset FROM post.id To person.id > > But for sure it's a link and not a edge. But maybe this could work. And > now I search for those LINK and on every of them I create an EDGE. Wow this > is very crappy but until it does not work it seems to be the best approach. > ;) > > Am Donnerstag, 21. August 2014 15:36:07 UTC+2 schrieb Curtis Mosters: >> >> How is it possible to create an edge for creating a relationship between >> *person >> *and *post*. >> >> CREATE edge hasAppln FROM (select FROM person) TO (select FROM post) >> >> I already tried it with >> >> CREATE edge hasAppln FROM (select FROM person) TO (select FROM post) >> where person.id = post.id >> >> but it just combines everything. Let's say I have in both table 2 >> entries, so I get 4 edges. The Where is completely ignored somehow. Another >> thing is that this query on 4 entries takes 0,2 seconds. So this is not >> practicable. Is there another way to do that? >> > -- --- 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.
