I don't think that's a problem.
As we've seen for years PostgreSQL users will quite happily and naturally remind everyone how much superior it is to MySQL (and every other database) at every opportunity.
As we've seen for years PostgreSQL users will quite happily and naturally remind everyone how much superior it is to MySQL (and every other database) at every opportunity.
* you don't need transactions
* you don't need foreign key constraints
* you don't need ACID-compliance
Granted many of these don't apply anymore, but then legacies live on interaction-wise. This being said, I know very few real Pg users who harp on MySQL anymore. Most of us figure that Oracle does better advocacy on this area than we can.
More like, technically true, but contrary to the whole reason for doing what they're doing.
Nobody puts a lot of work into something "honestly" not intending to replace the thing it's replacing.
They say this to appease the people who point out that it doesn't do all the same things.
If I built a better alternative to a common item, you could bet your bottom dollar i would be very "honest" about it not replacing that common item. The last thing that statement would be is "honest." It's appeasement.
I also think the best way to look at NoSQL is that it is just a further development on Stonebreaker's bottom-left quadrant database division--- object databases.
The more I get into it, the more I am astounded with the power of PostgreSQL to take over all these workloads on the low-end and more.
Exactly. When NoSQL "honestly" say, oh nooooooooo we're not replacing the traditional RDBMS approach, this is anything but honest.
It's like me building this suspended-rail system for inner-city transportation. Oh noooooooo I'm not replacing traditional cars and bicycles!
the way you get acceptance is by faking honesty that you're not at all replacing the traditional approach (that you're replacing.)
The power of PostgreSQL occurs from the power to ignore the relational model and take other approaches when it is helpful.