o apply the log then append any running transactions to the new log
This might be the heart of the problem. Dealing with running transactions. I
guess, for this reason, there is good merit in making all database access
that does not explicity focus on writing to the database, use readonly
On Fri, Oct 30, 2009 at 5:31 PM, Craig Taverner cr...@amanzi.com wrote:
Hi Johan,
Of course I have a response to each of your excellent points :-)
*'transactional merge'*
I do assume that all database access is locked for the duration of the real
'merge'. But since the merge should be a set
Hi,
It would be possible to implemented it but as I said it would require
a lot of work. The hard part is to merge the bulk loaded data set in a
safe *transactional* way.
The problem I see with it is that the data you are bulk loading have
to be independent of the rest of the graph. This is
Hi Johan,
Of course I have a response to each of your excellent points :-)
*'transactional merge'*
I do assume that all database access is locked for the duration of the real
'merge'. But since the merge should be a set of raw file concatenations, I
assume that does not take too long (seconds, I
Hi,
Recently Johan pointed out to me that merging databases was not something
easily added to the core neo4j because there would be clashes of ids.
However, I have thought a bit more about it, and I think there is a way this
can work (in theory) for special cases.
Here is my example:
- We
5 matches
Mail list logo
