News for hackers. Stuff that matters.
Re:MySQL vs PostgreSQL by cbrinker on Thursday October 09, 2008 @09:17PM (#328464)
Well, I pose to you this question:

Would you rather have 1 type of car that the government makes that works pretty reliably and is a middle-ground car, or would you rather have a selection of cars to chose from; sports, truck, sedan, minivan, etc. ?

Everyone has different needs. I use MySQL extensively for it's memory-based storage engine, MyISAM for quick & dirty non-escential data i/o, and InnoDB for when data needs to be managed securely for processes.

I would use PG for transaction-based data processing in a high-volume situation with multi-processing clusters. Otherwise MySQL works fantastic for all my needs.

Re:MySQL vs PostgreSQL by samuel on Friday October 10, 2008 @02:00AM (#328630)
The flexibility is great, but only if grouped with consistency. No foreign keys on MyISAM but yes on InnoDB? Thanks but no, thanks.
Re:MySQL vs PostgreSQL by thwarted on Friday October 10, 2008 @05:19AM (#328682)
No disk backed storage with heap tables but yes on InnoDB? Thanks but no, thanks.

Uh, the definition of flexibility is lack of consistency between the options. Otherwise, it's a false choice.

Re:MySQL vs PostgreSQL by davidw on Friday October 10, 2008 @07:06AM (#328728)
I've always preferred the bicycle analogy: MyISAM is like a bicycle with no brakes. It goes real fast down hills, unless something goes wrong.
Re:MySQL vs PostgreSQL by earthboundkid on Friday October 10, 2008 @06:41AM (#328718)
Car analogies?

Well, I pose you this question:

Would you rather have a car that runs into a wall and explodes and kills everyone inside or no car at all? The car is like using car analogies on Slashdot and not having a car is like not using car analogies on YC.

In conclusion and in summary, go back to Slashdot. KTHXBAI.