I inspected my OrientDB database carefully. It seems that OrientDB created a lightweight edge between parent and child nodes. However, edge information is only stored at child node, but not in parent node. So that is why if I navigate from child I could reach parent, but not the other way. Does anyone know how this could happen? I thought OrientDB automatically put edge information on both vertices.
Tai On Wednesday, April 20, 2016 at 3:54:52 PM UTC-4, Tai Hu wrote: > > I just upgrade from OrientDB 2.2.0-beta to OrientDB 2.2.0-beta2 and > noticed two serious issues with my application. > > 1. With OrientDB 2.2.0-beta2, our application build for Windows 32bit will > hang at start up. I checked log file, it seems that when OrientDB engine > starts, it complained that DISKCACHE is too small, then block the running > thread. All other build on Windows 64bits and Mac OSX are starting up fine. > > 2. My application open an existing graph db (created by 2.2.0-beta) and > created a child node with an out edge to parent node. If I search child > node, I could find it and navigate from child node to parent node. However, > if I search parent node and try to navigate from parent node to child node. > It cannot reach child node. > > I copied this graph db into OrientDB studio and use Graph DB View to check > this database. > > select from child where name = "childname" > > I could see that child node on canvas. Then if I double click on that > child node, it will expand with an out edge to parent node. > > However, if I do > > select from parent where parent = "parentname" > > I could see the parent node on canvas. Then if I double click on that > parent node, it will not expand to show child node which connected to it. > -- --- 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
