I don't think that's a very good idea to have as a default behaviour
since potentially the entire graph is interconnected (and that it
isn't just a tree structure), deleting one node could potentially
delete the entire database.
We could however have some kind of utility where you specify criteria
Any plans to support cascade deletion?
We currently have some cases where we have to manually iterate over
the relationships and remove them.
Not a big deal because we wrap many other operations but something
that would nice to have out of the box.
2010/2/9 Mattias Persson :
> Yep, that's right...
Yep, that's right... The documentation is a bit unclear/untrue about
that. Ryan is right in that it's only checked when the transaction is
commited. This means that you can delete a node which has
relationships on it, just as long as you delete its relationships
before the transaction is committed.
Well, it's not totally untrue. Try changing your tx.failure() to tx.success()
and you'll get the error you're looking for. Neo is a fairly transaction
driven database and I imagine it doesn't check the constraints of the delete
until it's committed.
On Feb 9, 2010, at 3:28 PM, Stefan Armbrust
Hi,
it looks like Node.delete() does not behave as defined in the API docs:
Deletes this node if it has no relationships attached to it. If delete()
is invoked on a node with relationships, an unchecked exception will be
raised. Invoking any methods on this node after delete() has returned is
inv
Hello johan,
apo...@mars:~$ java -version
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
apo...@mars:~$ uname -svr
Linux 2.6.28-18-generic #59-Ubuntu SMP Thu Jan 28 01:40:19 UTC 2010
On 8 February 2010 2
6 matches
Mail list logo
