Setting a property to null should remove that property
Reported by Andreas Ronge | December 17th, 2008 @ 10:19 AM | in 0.1
Since neo4j does not accept null properties one way of handling it is to remove that property from the node. Also getting a property that does not exist will return nil
Comments and changes to this ticket
-
Andreas Ronge December 17th, 2008 @ 04:17 PM
- State changed from “new” to “resolved”
(from [94938a49699e4d59367d5266c14f43ca540cf197]) Impl remove properties and marshalling of properties of any type. Updated RDocs. [#3 state:resolved]
[10 state:resolved] http://github.com/andreasronge/n...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Neo4j.rb is a graph database framework for JRuby.
It provides:
* Mapping of ruby objects to nodes in networks rather than in tables.
* Storage of ruby object to a file system.
* Fast traversal of relationships between nodes in a hugh node space.
* Transaction with rollbacks support.
* Indexing and quering of ruby objects.
* Integration with Rails
Andreas Ronge