[wip] native JSON support

[aol-nnov]

Hi!

I was i need of JSON data type power which PostgreSQL provides, so I've started working in this direction.
It seems, that there is a demand for that support already: #31, #7, so, @gebrits, @kesavkolla I invite you to collaborate in this area if you still interested.

@raymondfeng what do you think about enabling certain features in the connector (upsert support, json, whatever) based on the database version? Where in the code is the best way to test the DB version and fill a set of supported features? Should it be done automatically or set via config? Also tell me please what do you think about mods in this PR?

[aol-nnov]

nice articles that helped me a lot:
http://www.postgresql.org/docs/9.3/static/functions-json.html
http://schinckel.net/2014/05/25/querying-json-in-postgres/

[kesavkolla]

Actually my example is bad. The escapeName doesn't even do anything with select columns. The escapeName is only called from createTable and columns to be dropped. So there is no need to touch that code in my opinion.

[jmls]

did this stall here ? It would be useful to have the 9.4 json datatypes in place now

[aol-nnov]

@jmls sad to say, I've dropped it completely. Moved away from loopback and using bookshelf.js currently.

[jmls]

@aol-nnov : That's not good to hear. May I ask why ?

[aol-nnov]

@jmls well, it was a long way to go :)
first of all, I had to wrap my head around all the guts loopback have. And the best way was to start something similar from scratch, lol.
secondly, I needed better postgresql support, and, to be frank, I really love bookshelf and knex.
and my app is not only api, but a web frontend too (well, it actually does not count as an argument and I could build web frontend atop of loopback)

[ZepAviator]

Having JSON / JSONb support would be great. It seems that maybe some ideas for code on these properties types could be pulled from the nosql connectors?

Anyone have any branches of working JSON type?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[slnode]

Can one of the admins verify this patch?

[slnode]

Can one of the admins verify this patch?

[slnode]

Can one of the admins verify this patch?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

[zbarbuto]

FWIW #304 was merged recently