3 ms·

It seems you could easily get a nosql postgres if you limit yourself to one table with two columns (id, json). Snark apart, it would work quite ok, no?

by gbog 13y ago

masklinn 13y ago
the json support is fairly recent and doesn't support operating directly on the data yet (e.g. you have to create functional indexes through plv8js and you can't directly query on the document's content as you can with array, xml or hstore columns)
- jeltz 13y ago
  PostgreSQL 9.3 adds functions for accessing JSON data without having to use plv8js.
  - masklinn 13y ago
    Yeah but since it's just being added, it precludes "NoSQL guys" having built upon it, which is the original complaint.
    - jeffdavis 13y ago
      Another intepretation of zapov's comment is that it's a shame the NoSQL projects didn't try achieving their goals by building postgres extensions (or even adding new features). A reasonable question. MongoDB could have focused their energies on really good JSON support in postgres and making postgres sharding easier.
      - masklinn 13y ago
        An interesting interpretation, which I had not considered. Thank you.
- e1ven 13y ago
  I'm using https://github.com/JerrySievert/mongolike https://github.com/JerrySievert/mongolike to support Postgres using mongo-like queries. I patched in a bunch of features I needed, and it works really well for me.
recuter 13y ago
Sort of like a column store? ;) This is also rather how Reddit uses it I believe.
lucian1900 13y ago
You'd be better of with hstore than json.
snaky 13y ago
If there would be HandlerSocket or similar, yes.
- karavelov 13y ago
  Postgresql has prepared queries - they give you the same type of optimization (skip the query parsing on each execution) with more flexibility and with SQL standard syntax.
  - snaky 13y ago
    Prepared statements are far away from speedup you may get with handlersocket, even with https://github.com/dimitri/preprepare https://github.com/dimitri/preprepare

It seems you could easily get a nosql postgres if you limit yourself to one table with two columns (id, json). Snark apart, it would work quite ok, no?

by gbog 13y ago

It seems you could easily get a nosql postgres if you limit yourself to one table with two columns (id, json). Snark apart, it would work quite ok, no?

masklinn 13y ago

the json support is fairly recent and doesn't support operating directly on the data yet (e.g. you have to create functional indexes through plv8js and you can't directly query on the document's content as you can with array, xml or hstore columns)

jeltz 13y ago
PostgreSQL 9.3 adds functions for accessing JSON data without having to use plv8js.
- masklinn 13y ago
  Yeah but since it's just being added, it precludes "NoSQL guys" having built upon it, which is the original complaint.
  - jeffdavis 13y ago
    Another intepretation of zapov's comment is that it's a shame the NoSQL projects didn't try achieving their goals by building postgres extensions (or even adding new features). A reasonable question. MongoDB could have focused their energies on really good JSON support in postgres and making postgres sharding easier.
    - masklinn 13y ago
      An interesting interpretation, which I had not considered. Thank you.
e1ven 13y ago
I'm using https://github.com/JerrySievert/mongolike https://github.com/JerrySievert/mongolike to support Postgres using mongo-like queries. I patched in a bunch of features I needed, and it works really well for me.

recuter 13y ago

Sort of like a column store? ;) This is also rather how Reddit uses it I believe.

lucian1900 13y ago

You'd be better of with hstore than json.

snaky 13y ago

If there would be HandlerSocket or similar, yes.

karavelov 13y ago
Postgresql has prepared queries - they give you the same type of optimization (skip the query parsing on each execution) with more flexibility and with SQL standard syntax.
- snaky 13y ago
  Prepared statements are far away from speedup you may get with handlersocket, even with https://github.com/dimitri/preprepare https://github.com/dimitri/preprepare