Allow non-string type properties to survive this workaround

I discovered this problem while trying to set a new node property to a non-string value, e.g.,

node = Neo4j::Node.new
node[:foo] = 4

Not sure if this is useful (considering the comment above says it's a workaround), but I'll let you make that decision :-)

All the best,
-Shane