> From: *Eddy Respondek* <[email protected]> > Date: Wed, Sep 14, 2011 at 11:30 AM > To: [email protected] > > > This may be a little off topic but maybe someone has done something similar > before. > > Basically I have a separate Wordpress site (php/mysql) which I've been > extending significantly and I've setup another server on the same network > for graph db testing (neo4j/tinkerpop/python-bulbs). I'm confident with my > graph setup now and would like to attempt to get something small into > development so I can monitor the results. I want to do a simple "like" > relationship between users and articles. > > That means I need to keep an identical index of user ids and article ids in > the graph db. I know how to update the id's when a new user or article is > created, deleted, etc. What I don't know is the correct way to ensure data > integrity in case something goes wrong like the graph db server crashes, > etc. > > Does anyone have any thoughts on the best way to do this? > I store the last loaded IDs as properties on the root node, then every time my sync script is run it loads everything from those IDs forward, checking as it goes that it doesn't create duplicates. It's not the fastest way, but it's robust. If the graph DB becomes corrupt, you roll back to the latest back up and rerun the sync.
(We have the advantage that our data is immutable - you'll need some extra changes if that isn't the case for you, but can use the same general technique) Xavier _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
