Hi!
This is awesome!
I tried it out and have a suggestion: to make the semantics for "storing
NULLs" consistent you could change the PropertyContainer::__set method
to remove the property if it exists when trying to set it to NULL. This
will make sure NULL is returned when you try to read the property.
Something along the lines of:
public function __set($k, $v)
{
// because neo doesn't store NULLs
if ($v===NULL)
{
if (array_key_exists($k, $this->_data))
{
unset($this->_data[$k]);
}
}
else
{
$this->_data[$k] = $v;
}
}
For some reason calling Node::save twice gives me an exception, so I
can't update a node after the first save and save it again with new
property values. Maybe a bug?
/anders
On 06/02/2010 01:00 AM, Alastair James wrote:
> Hi there!
>
> Sorry, been a bit quiet on the PHP REST API front for a few weeks.
>
> I will be added some features this week (traversals etc...), but in the mean
> time, I have (finally) written up a little blog post detailing how the
> current version works!
>
> http://onewheeledbicycle.com/2010/06/01/getting-started-with-neo4j-rest-api-and-php/
>
> Stay tuned for more!
>
> Alastair
> _______________________________________________
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
