Hi Curtis, I think this behavior was introduced by commit b2c9317f7db3dee26a075d186d32c9eaf6803f21 IMHO the fix should consist in writing a Map implementation that behaves like OrientElementIterable, and just add an IF in that method. @laa, @tglman WDYT?
Luigi 2015-09-11 21:33 GMT+02:00 Curtis Stanford <[email protected]>: > This is still causing me grief. Isn't there any way to get a LINK MAP > (i.e. Map<String, ODocument>) from a vertex? The problem with using > vertex.getRecord().field("propName") is that any changes to the map are not > persisted to the vertex. I have to do a vertex.setProperty("propName", map) > to persist it but I'm not sure that's very performant for a small change to > a large map. > > The problem now seems to be lines 287 - 289 in OrientElement.java: > > if (graph != null) > // CONVERT IT TO ITERABLE<VERTEX/EDGE> > return (T) new OrientElementIterable<OrientElement>(graph, > OMultiValue.getMultiValueIterable(fieldValue)); > > I guess the question is, is there any way to get a LINK MAP from a vertex, > make a small change to the map, and have it persisted after the transaction > is committed? (Using the Java API) > > Thanks! > > -- > > --- > 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.
