Hi Craig,
Thank you, thank you for this wonderful response - it is probably the best
response I have received on this forum ever!! ;) and gives me a lot of food
for thought.
I am currently indeed using heavyweight edges, the reason is because we
need to put a date stamp on many of our links and I think HW is the only
way to achieve that? that said in this particular case (the bulk import I
am struggling with here) we do not need dates so perhaps lightweight links
are the way to go. Is it possible though to use a combination of HW and LW
between different vertex in the some DB?
i.e.
A has B is LW
B relates C is HW with a date field
The reason I ask is that in the OrientDB Studio application I have seen a
setting to turn lightweight edges on or off (useLightweightEdges) this made
me think that you have to chose one or the other when you build a database,
or perhaps this is to do with the rendering of edges within the graph page
of the studio. If I use LW eges will I still be able to use the OrientDB
Studio graph functionality? I am guessing not...
As for the 'does this edges exist' check - I am not actually doing that
since I have managed to pre-load and sort all the data so I already know
the RIDs of both ends of the edge before I start. I am literally just doing
millions of
graph.addEdge("class:from_relates_to", fromVertex , toVertex ,
"from_relates_to").save();
I am pretty sure changing that to use LW edges would be a massive
performance improvement but I am not really sure what the create
lightweight edge syntax looks like.... is it magic only if 'useLightweight'
is true??
Simon
--
---
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.
