git-svn-id: https://svn.erp5.org/repos/neo/trunk@2547 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2546 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2545 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2544 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2543 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2542 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2541 71dcc9de-d417-0410-9af5-da40c76e7ee4

This query happens when a storage node joins the cluster, to delete all
rows belonging to partitions it is not assigned to (ex: storage was down
and partition table was reorganised before it rejoined cluster).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2540 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2539 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2538 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2537 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2536 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2535 71dcc9de-d417-0410-9af5-da40c76e7ee4

This allows parallel execution of tpc_begin, stores & related conflict
resolution and tpc_vote for different transactions.
This requires an extension to ZODB allowing to keep TID secret until
tpc_finish (ie, so that it doesn't require tpc_vote to return tid for each
stored object).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2534 71dcc9de-d417-0410-9af5-da40c76e7ee4

If TID allocation and conflict resolution are serialised at database scope
(=cluster scope in NEO), the question doesn't arises: when we have a TID,
we are the latest TID until we call tpc_finish.
If they are not serialised, it means TID allocation will happen after
conflict resolution, as TID generation must be serialised anyway, and in
such case, the temporary TID we have when detecting conflicts has no
ordering signification, so it is meaningless to check their chronology.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2533 71dcc9de-d417-0410-9af5-da40c76e7ee4

Remove round-trip to master upon "load" call.
Move load/loadBefore/loadSerial/loadEx from app.py to Storage.py.
This is required to get rid of master node round-trip upon each "load"
call.
Get rid of no-op-ish "sync" implementation.
Separate "undoing transaction ID" from "undoing transaction database
snapshot" when undoing.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2532 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2531 71dcc9de-d417-0410-9af5-da40c76e7ee4

This ensures invalidations are sent in strict ascending TID values order.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2530 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2529 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2528 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2527 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2526 71dcc9de-d417-0410-9af5-da40c76e7ee4

This is done by benchmark test runner too.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2525 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2524 71dcc9de-d417-0410-9af5-da40c76e7ee4

Rationale: dispatcher will refuse answer of a type which doesn't match
request, and this is tested separately.
Also, remove now-useless references to txn_finished.
Fixes regressions introduced in r2517.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2523 71dcc9de-d417-0410-9af5-da40c76e7ee4

Also, don't expect setTransactionFinished/setTransactionVoted to be called.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2522 71dcc9de-d417-0410-9af5-da40c76e7ee4

It broke ZODB tests.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2521 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2520 71dcc9de-d417-0410-9af5-da40c76e7ee4

Storage doesn't vote here, it only stores transaction metadata. And we do
want to make sure it was stored at least once.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2519 71dcc9de-d417-0410-9af5-da40c76e7ee4

It was actually used to track individual answerStoreTransaction, and there
is no need to track them individually.
Instead, just set txn_voted to True before returning, so it really means
that tpc_vote ended successfully.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2518 71dcc9de-d417-0410-9af5-da40c76e7ee4

The only alternative to this is raising (either because there was no
answer, or because the answer didn't satisfy our handler).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2517 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2516 71dcc9de-d417-0410-9af5-da40c76e7ee4

Also, fix bogus checkCurrentSerialInTransaction implementation (it was not
properly locking object, allowing them to become non-current by the time
tpc_finish occurs).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2515 71dcc9de-d417-0410-9af5-da40c76e7ee4

...and fix its declaration.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2514 71dcc9de-d417-0410-9af5-da40c76e7ee4

undoInfo comes from BaseStorage, which inherits it from UndoLogCompatible.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2513 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2512 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2511 71dcc9de-d417-0410-9af5-da40c76e7ee4

Also, some manual tweaks to fix easy differences between implementation and
interface / related comments:
- make name unique (provided name option is itself unique)
- __name__ property definition is delegated to BaseStorage.__init__
- warn about _is_read_only as being somewhat part of the interface
- make "load"'s "version" mandatory, and assert it is ''
- store: likewise
- registerDB shouldn't require a second argument
- note that tpc_begin doesn't follow interface described behaviour when
  a commit is already running. This is a feature actually, and should be
  harmless to caller.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2510 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2509 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2508 71dcc9de-d417-0410-9af5-da40c76e7ee4