2009/12/26 Laurent Laborde :
> On Sat, Nov 21, 2009 at 11:35 AM, Laurent Laborde wrote:
>>
>> My neo4j database won't be "critical" for the production, it can go
>> down and/or crash at anytime without breaking the production platform.
>> But... populating this database will take a lot of time and
Hi Laurent!
> The next step will be the exploitation of the content of the database.
> Neoclipse gave up a long time ago, i am expecting around 20.000 nodes
> and ... mmm... a million relationship (with different type) ?
>
What limits Neoclipse is the number of nodes/relationships which can b
On Sat, Nov 21, 2009 at 11:35 AM, Laurent Laborde wrote:
>
> My neo4j database won't be "critical" for the production, it can go
> down and/or crash at anytime without breaking the production platform.
> But... populating this database will take a lot of time and some
> usefull ressource. So i'll
On Fri, Nov 20, 2009 at 7:58 PM, Peter Neubauer
wrote:
> Laurent,
> the reference node does not _have_ to have a relationship, although it
> is not recommended not to do so.
But all my DB *will* have a reference node with relationship, so it's
safe to assume that a DB with a reference node withou
Laurent,
the reference node does not _have_ to have a relationship, although it
is not recommended not to do so.
Another way to do this is to see if there are any relationships/nodes
in use. This is not the official API, but there is the possibility to
get a TransactionManager and the number of ID
I don't know if this is best practice but I have in the passed used
the ref node to store stats about the graph, I.e. Node count,
relationship count etc
D
On 20 Nov 2009, at 14:54, Mattias Persson
wrote:
> 2009/11/20 Laurent Laborde :
>> Aditionnaly, i think that i found the easiest way to
We also moved to the 'create on demand' approach largely because we often
make enhancements to the application and required data structures, but run
on older databases, so it is nice if the app can 'update' the database.
Doesn't always work, but reduces the number of times we need to delete the
ent
2009/11/20 Laurent Laborde :
> Aditionnaly, i think that i found the easiest way to know if i run a
> new database for the first time :
> if(referenceNode.hasRelationship() == false) {
> //we are running this database for the first time
> //initialize stuff.
> }
Sounds like an excellent id
Aditionnaly, i think that i found the easiest way to know if i run a
new database for the first time :
if(referenceNode.hasRelationship() == false) {
//we are running this database for the first time
//initialize stuff.
}
On Fri, Nov 20, 2009 at 1:13 PM, Mattias Persson
wrote:
> Great,
Great, I'd be glad to answer more questions as they come along... and
enjoy your lunch!
Best,
Mattias
2009/11/20 Laurent Laborde :
> Thank you for your very fast replies.
> I will have more question, soon.
> But it's time to eat and i'll have some code to do before jumping to
> the next problem.
Thank you for your very fast replies.
I will have more question, soon.
But it's time to eat and i'll have some code to do before jumping to
the next problem.
--
Ker2x
sysadmin & DBA @ http://www.over-blog.com/
___
Neo mailing list
User@lists.neo4j.org
h
2009/11/20 Laurent Laborde :
> Mmmm ... and if i want to store the, eg, "latest updated node before
> clean shutdown" ?
> I create a relationship "to_latest_updated_node" from referenceNode to
> this Node before shutting down ?
Sure, that'd be good for that as well.
>
> --
> Ker2x
>
>
> On Fri, Nov
2009/11/20 Laurent Laborde :
> On Fri, Nov 20, 2009 at 12:19 PM, Mattias Persson
> wrote:
>> 2009/11/20 Mattias Persson :
>>> The best way to achieve that is to create relationships to those
>>> nodes... such as
>>>
>>> ReferenceNode --[CONFIGURATION]--> ConfigurationNode
>>> ReferenceNode --[INDE
Mmmm ... and if i want to store the, eg, "latest updated node before
clean shutdown" ?
I create a relationship "to_latest_updated_node" from referenceNode to
this Node before shutting down ?
--
Ker2x
On Fri, Nov 20, 2009 at 12:19 PM, Mattias Persson
wrote:
> 2009/11/20 Mattias Persson :
>> The
On Fri, Nov 20, 2009 at 12:19 PM, Mattias Persson
wrote:
> 2009/11/20 Mattias Persson :
>> The best way to achieve that is to create relationships to those
>> nodes... such as
>>
>> ReferenceNode --[CONFIGURATION]--> ConfigurationNode
>> ReferenceNode --[INDEX]--> IndexNode
>> a.s.o.
>>
>> That's
2009/11/20 Mattias Persson :
> The best way to achieve that is to create relationships to those
> nodes... such as
>
> ReferenceNode --[CONFIGURATION]--> ConfigurationNode
> ReferenceNode --[INDEX]--> IndexNode
> a.s.o.
>
> That's more of a neo-style-approach. The node ids persist over time
> until
The best way to achieve that is to create relationships to those
nodes... such as
ReferenceNode --[CONFIGURATION]--> ConfigurationNode
ReferenceNode --[INDEX]--> IndexNode
a.s.o.
That's more of a neo-style-approach. The node ids persist over time
until they are deleted and deleted ids may be reus
Friendly greetings !
I'm a new user and... not a coder. I'm sysadmin & Postgresql DBA at
http://www.over-blog.com/
I'm confused about the documentation.
I'm not 100% sure that a nodeID persist over time, restart, update.
Can you tell me please ?
I'd like to store in the referenceNode some infor
18 matches
Mail list logo
