Hi,
I have also built some versioning concept on Neo before.
Essentially, my solution is based on two kinds of objects:
- VersionedObject represents the identity of something. It references
ObjectVersions.
- ObjectVersion represents a version of the object, there can be many
and they point to
Hi Peter,
The separation of identity and version of objects is a good point.
The way you have modeled things, are all active relationships at a
particular version present at that version node, or is the set of
relationships made up from all version nodes all the way back to the first
version of
Hi again,
The way you have modeled things, are all active relationships at a
particular version present at that version node, or is the set of
relationships made up from all version nodes all the way back to the
first
version of an object.
in my case, all relationships are copied. For my
Andreas,
I had a look at this and realized problem is caused by the static
nature of SpringTransactionManager and UserTransactionImpl. A fix for
this has been on my todo for some time but to make it right we need to
expose some new stuff in NeoService (mainly tied to configuration API
that has
Well, basically it's the ame idea here. However the Shell have had
scripting support from day one for Groovy and Jython (can of course
add one for Ruby as well) using commands gsh and jsh respectively, but
I'm thinking more about a simple traverser command where you don't
want to hack a script
Of course the scripts will have to exist server-side, but that can
change too so that you point to a script file in the client or write a
small script in the prompt and send down to the ShellServer.
2009/5/20 Mattias Persson matt...@neotechnology.com:
Well, basically it's the ame idea here.
Johan,
First of all thank you for quickly addressing my issue. I tested it and things
work just fine.
Still, I took the liberty to actually refactor your solution slightly different
hoping you could review the change and commit it to trunk. My code change
mainly frees the transaction manager
On Thu, May 21, 2009 at 02:06, Andreas Guenther
aguent...@flying-orange.com wrote:
This also avoids casting NeoService down to EmbeddedNeo, which I frankly
have seen too many times in the code base, and really suffered under with my
own NeoService wrapper implementation ;) Anyhow, I understand
I should probably outline how spring configuration looks like with
my change. It's pretty similar to before with two constructor changes:
bean id=neoTransactionManagerService
class=org.neo4j.impl.transaction.SpringTransactionManager lazy-init=false/
bean id=neoUserTransactionService
9 matches
Mail list logo
