Hi, You should consider graphdb instance as connection instance, merely use pool and open/close create db on each request. Such approach does not add any overhead.
On Fri, Jul 24, 2015 at 11:03 AM Vianney Grassaud <[email protected]> wrote: > I found a workaround and I follow your documentation to use OrientDB in a > web application. > > So, I implemented a servlet filter, this filter get OrientGraph from the > factory, invalidate the localcache and close the graph at the end. > > Is it a good solution ? > > > Le jeudi 23 juillet 2015 19:56:21 UTC+2, Vianney Grassaud a écrit : >> >> Hi, >> >> I have an application using Rest API. >> >> But, I have some troubles with the cache level1 of OrientDB. >> >> I update a Vertex by calling a rest service. >> >> If I call a second rest service that loading the same vertex that was >> updated previously, it doesn't have the good version because the rest call >> is in another thread and so, the database instance and the cache are >> different >> >> Finally, I get CME... (when i modified graph), but on reading operation I >> can get bad version of my data. >> >> So, how to invalidate the cache level 1 on each database opened by the >> OrientGraphFactory each time I commit a changing ? >> >> >> -- > > --- > 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.
