Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NoSQL No More

technosophos.com

Post reply on HN
Print view View original

61–62 of 62 posts

Re: NoSQL No More

#61

Post by Sanddancer »

fidotron wrote: post #11
DrJokepu wrote: post #3

This is why PostgreSQL is awesome. You can freely mix relational with non-relational (object) storage depending on your needs.

This is only if you ignore why people moved to NoSQL in the first place. PgSQL is great for a lot of things, but I would argue that if you're using it you're betting on your overall product/service having some other killer advantage than data processing. The competent wing of the NoSQL crowd are using it in strange ways that enable new classes of product and service that cannot be achieved with PgSQL.

I get the feeling you're comparing NoSQL to what PgSQL was 4-5 years ago. Modern PgSQL has a pretty rich set of tools for handling schemaless data, and combines that with its traditionally strong support for relational data. PgSQL has a direction that cares a lot more about data than doctrine.

Though your last line makes me curious. What is an example of one of these new classes of product and service that can't be achieved with PgSQL?

Re: NoSQL No More

#62

Post by vertex-four »

mrcsparker wrote: post #60
vertex-four wrote: post #40

Earlier quoted context omitted.

The point is that someone has to actually sit down and define the exact feature set that a WebSQL implementation is supposed to implement, such that a development team could sit down with a copy of the standard and no other code and implement their own WebSQL implementation from scratch. The fact that SQLite is available is entirely irrelevant to any of this. The W3C can't just say "do it like SQLite does it" - that'…

I don't understand this argument. There is already a SQL standard. Start there.

The SQL standard defines far more than you'd want in a web browser, and I'm not sure anyone actually wants all of it. So someone has to sit down and define which bits to cut out, anyway... and then browser developers have to develop a database engine, which I'm fairly sure none want to do. We barely have any open-source software that implements SQL correctly as it is.
Post reply on HN