will be registered at the revision, and on commit everything will be
stored in the database.
regards,
Peter
-Original Message-
From: Georg M. Sorst [mailto:georgso...@gmx.de]
Sent: Montag, 26. April 2010 18:00
To: user@lists.neo4j.org
Cc: Peter Haensgen
Subject: Design pattern for versioned
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 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
Hi,
The mapping to nodes and relationships is easy, if you have a node
type:
- User -- Node {type = User}
- UserGroup -- Node {type = UserGroup}
- members -- Relationship {type = members}
- admins -- Relationship {type = admins}
I'm not sure I follow you here. Does relationships
Hi there,
Last week Tobias wrote a great wrap up about node types:
http://journal.thobe.org/2008/12/about-types-in-neo4j.html
Among other stuff he mentions the power of giving nodes multiple types
(by using different relationship types).
So now I have a question for all of you: any
Hi all,
since I don't agree with some of the comments from Robert I just want to
give my feedback as well.
Well first I found I couldn't run it without the Shell and JTA jars.
I
wouldn't mind but the documentation implied that if you just want to
embed a graph db and go you only need the
Hi,
-- Import -- Neo4j Examples -- (list of example projects)
I have to correct myself:
The typical way is File -- New -- Example... -- (list of
example projects in a Neo4j group)
Yes, sounds great. You would open the example projects in your normal
Eclipse installation and run them, and
Hi,
has anyone implemented an object binding framework for Neo? I imagine
sth. that allows to define fields and relationships in POJOs using
annotations, and binds them using runtime code generation or
reflection.
no, I haven't, but I believe your question could also be read as: How do
I
Hi!
I fixed this bug in r2079 :-)
The traversal for nodes only looked for outgoing nodes. In the node
spaces I tried, the relationships to the reference node were incoming.
Hmm. But isn't this a design problem of your example? The screenshot
looks strange. ;-)
Why should there be an
I don't get any matches. What could I possibly be doing wrong?!
Hmmm. Is your graph viewer showing something?
What happens if you enter a number? This should find the node with this
id.
___
Neo mailing list
User@lists.neo4j.org
Hi!
Random Neoclipse stuff ...
As seen from the attached image, the properties of relationships are
presented such that the Properties part comes first, then the
Relationship part. For nodes it's the opposite (Node part comes
first). Is this behavior OK?
This is due to the fact that the
I like it. And I'm very happy that you didn't use the Ape icon for
Peter. ;-)
Good luck for the Eurocup tonight,
Peter
Now I have implemented icons and colors for the nodes (see
attachments).
Also did a lot of restructuring and cleanup.
Some choices i made:
- the same property names list
All formalieties done and Anders now has commiter rights to neoclipse.
Peter H, I assume this is ok with you as well?
Of course. I don't want to do everything myself. ;-)
Peter
___
Neo mailing list
User@lists.neo4j.org
Hi!
I pasted the error log when running the launch configuration below.
As I understand you, you got the source code, everything compiles fine,
but when starting the runtime instance of your Eclipse you get the
posted errors?
Can you check, if your run configuration has Launch with: all
,
and
object-creation in Java is cheap compared to long-lived objects...
My two Roubles,
(Over in Mother Russia this week)
Cheers,
-V
On Mon, May 5, 2008 at 11:20 AM, Peter Haensgen [EMAIL PROTECTED]
wrote:
Hi,
the enum approach has the disadvantage that the available
Hi,
the enum approach has the disadvantage that the available relationship types
are static, e.g. they must be known at compile time. In some cases, this may
not be sufficient.
Therefore I have built a DynamicRelationType, which simply looks like this:
public class DynamicRelationshipType
Hi all,
If the API is stable, another variant would be to import the Neo API,
and deploy the Neo libs as a separate bundle/plugin with its own
version handling. Right now, the Neo deps are embedded into the
plugin, which makes separate upgrade of the Neo kernel impossible.
I agree that
... is committed.
It currently consists of one plugin org.neo4j.neoclipse.
Next steps:
* Provide icons (preferably in png format) in 16x16 and 32x32
pixels
* Check how neo binaries can be injected into the plugin by the
build process
* Check how the plugin can be integrated
Hi there,
I have been experimenting with Neo in the last couple of days. I think
it's a very interesting project!
However, I would be happy if someone could help me with some questions
that I have.
1. Finding of Nodes
When I create a node and do not connect it with the reference
Hi again,
2. Count of elements
Mmmh, AFAIK, the the iterator is implemented lazy, so there is no
iteration going on until you actually call next(). This saves
unnecessary processing but would require eager fetching to count all
elements. Not sure that is a strong enough requirement
20 matches
Mail list logo
