On Wed, May 6, 2009 at 10:11 AM, Mattias Persson
wrote:
> Looks nice and simple and it's probably completely alright to have the
> store fail on non-clean shutdowns and stuff like that.
>
> I'm wondering about this method though.
>
> void createNode( long id, Map properties );
>
> What do we ne
On Wed, May 6, 2009 at 5:50 PM, Lyudmila L. Balakireva wrote:
> I need some clarifications on API.
> Let say we are loading some adjacency list. How do we handle in this
> scheme that node already exists? Do we index the nodes after the
> insertion ( using for example getAllNodes operation?) .
I need some clarifications on API.
Let say we are loading some adjacency list. How do we handle in this
scheme that node already exists? Do we index the nodes after the
insertion ( using for example getAllNodes operation?) .
Thanks, Luda
> Hi,
>
> As you may or may not know, the Neo4j kernel i
Looks nice and simple and it's probably completely alright to have the
store fail on non-clean shutdowns and stuff like that.
I'm wondering about this method though.
void createNode( long id, Map properties );
What do we need that for? Couldn't that encourage an erroneous
behavior where you
Hi,
As you may or may not know, the Neo4j kernel is heavily optimized for
reads and transactional updates, which in a typical transactional
system probably constitute 95+% of the operations. So far, we haven't
focused on raw batch insert velocity, since that's typically a
one-time operation that y
5 matches
Mail list logo
