Support for REST format

[aseemk]

Quick bug first: extractData recursively calls itself if an object has a data property, so this means it'll incorrectly drop legitimate property data if there happens to be a property named data. =)

But wait! That bug's not worth fixing, because (I think) you don't even need that function anymore, since the transactional endpoint returns just property data by default now. So you should just remove it.

But on that note, I'd like to request an option to return the REST format instead of the lean property-only format. Having node and relationship metadata is needed for ORM/OGM-type libraries.

Easy enough to request it:

http://neo4j.com/docs/stable/rest-api-transactional.html#rest-api-execute-statements-in-an-open-transaction-in-rest-format-for-the-return

This could potentially be just another option to add to #10's options-based API, e.g. format.

WDYT? SGTY? ORLY?

[brian-gates]

Sorry I missed this issue!

I think your'e totally right! Which is awesome since it'll save some processing :) I'll take a look when I can.

If the REST format were requested, would we just emit the responses verbatim?

[aseemk]

Suh-weet, thanks!

You'd still do the dictionary-ifying thing (result[columns[i]] = row[i]), but within that, yep, you'd return the raw JSON verbatim.

[brian-gates]

Removed the extractData method: brian-gates@1c00cf3

[aseemk]

In pull #16, I didn't generalize this to format, because I realized that adding graph support would mean entirely different parsing. (The results are no longer simple arrays of column values.)