You may be interested in this article. May explain why MySQL makes it
while PostgreSQL doesn't.
http://www.jwz.org/doc/worse-is-better.html
-- G.
Begumisa Gerald M wrote:
Actually I do see this similar to the classic FreeBSD - Linux clash.
FreeBSD was built to be rock solid from the start (all kinds of controls
on the developers, making sure the quality of code was just the right,
having a *very high* level of organization including clear documentation
etc...) as a result its quite a reliable choice (I had over 340 days
straight uptime until someone where we're co-locating the box rebooted it
by mistake).
Whereas, Linux didn't quite start like that though with the latest 2.6
Kernel the two OSs seem to be converging (in security, scalability and
stability). MySQL was built to be lightening fast from the start and the
developers were very arrogant about features (they were reknown for saying
"transactions should be handled in the application code"), it surely was
quite fast but as it becomes a "corporate solution", there is increased
pressure for it to conform thus increasing "standard" features that an
RDBMS should have -- transactional support, prepared statements,
subqueries etc...
---------------------------------------------
This service is hosted on the Infocom network
http://www.infocom.co.ug
