This is a major refactoring of the type system in Cypher.
minor formating changes
Consoles in webadmin can now be disabled
…ng up strings
…ew chapter containing data modeling examples.
Typo fixes and rewordings to improve readability.
Placebo Transaction behavior
* no longer cached by InternalAbstractGraphDatabase * tx.success in UniqueNodeFactory * cypher: #681 transaction commit and failure handling now both in CommitPipe
…rnelData() which may bypass any proxy instance" This reverts commit 62e73bf as it broke several tests in server component (on CI system, not locally before pushing)
Revert to fix broken build
…r nested tx in updating operations" This reverts commit 43150be.
Cypher tx behavior
… tx in updating operations
…() which may bypass any proxy instance
o New common super-type for AbstractGraphDatabase and HighlyAvailableGraphDatabase. - Motivation: some users who built against Neo4j 1.6 depend on the internal AbstractGraphDatabase type. - Since HighlyAvailableGraphDatabase stopped extending AbstractGraphDatabase, we need a new type to avoid breaking backwards compatibility for these users. - The old AbstractGraphDatabase has been renamed to InternalAbstractGraphDatabase. - The new AbstractGraphDatabase has the same fully-qualified name as the old AbstractGraphDatabase and will be made binary compatible for consuming classes. o AbstractGraphDatabase defines all public methods of InternalAbstractGraphDatabase. - This ensures that any existing consumer of AbstractGraphDatabase will work without changes. - HighlyAvailableGraphDatabase delegates transactionRunning() to the local database instance. - transactionRunning() deprecated in preparation for removal in a later version. o Revert type of Database.graph to AbstractGraphDatabase. - The type of this field was previously changed to GraphDatabaseAPI. - Now reverting to a type with the same name and signature as the previous type to preserve backwards compatibility. - Also changing most usages of the field to use the GetGraph() accessor, as recommended by its deprecation comment.
The acquireReadLock method did not make sure to get the current transaction, so aqcuiring and releasing read locks was registered against different TransactionLockElements.
… fix for rollbacks, which didn't work. Specifically, changed locking to use a given transaction whenever possible, rather than discarding and trusting the TX manager to keep track of the tx for us.