Can you provide a stacktrace with the exception you're getting? My gut
feeling is that it's a classpath issue. Reading the stacktrace is
tromendously helpful and will often state exactly what the problem is. And
also if you could provide the source code for it (maybe as the next step
though).
I agree that startup/shutdown database in session lifecycle is not a good
idea. It'll cost more time during the startup/shutdown and will slow down
your application if you have a huge number of sessions.
On Sat, Jul 2, 2011 at 23:10, Mattias Persson matt...@neotechnology.comwrote:
Everything
Everything written to the database with successful transactions is persisted
and will be accessible in any following sessions. Just _don't_ think of a
GraphDatabaseService instance as a short lived object (like a SQL
connection), but instead see it more as your database server which benefits
from
Hi, I have a question about sessions in Neo4j. I'm working with the embedded
Java (not as a server) and I can load my data and query it between transactions
without trouble. My question is whether/how it's possible to shut down my
database at the end of a session and then access it in a new
I'm doing that, and it works fine.
Eelco
On Fri, Jul 1, 2011 at 12:49 PM, Vaccaro, Kristen M kvacc...@mitre.org wrote:
Hi, I have a question about sessions in Neo4j. I'm working with the embedded
Java (not as a server) and I can load my data and query it between
transactions without
5 matches
Mail list logo
