We are doing an initial trial of OrientDB for a new initiative at my
company. We have had some success, but are still working out a few issues.
My first question is very basic.
When doing a read from a transactional graph, shouldn't I get an updated
view of vertex properties after I commit and read again.
This is the most basic example that I can think of
We have a method that does nothing but read and prints a property value
void read(){
while(true){
def node = g.V('__id,'1').next()
println node.count
g.commit()
}
}
Then in another application we do an update to that node
void write(newCount){
def node = g.V('__id,'1').next()
node.count = newCount
g.commit()
g.shutdown()
}
What we notice is that the reading application, regardless of doing the
commit, never reads the update value.
Our actual use case is more complex, but this seems to be at the heart of
our issue.
We have a workaround that uses the connection pool and shutdowns the graph
after a read, rather than just committing. But we find that we still have
some reads that don't seem to be getting updated values. This may be do to
a connection that we did not shutdown, but we haven't found it yet.
The real question here is why don't I get updated values on read after I
commit?
--
---
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.
