From: Dick Davies <rasputnik@...>
Date: 2004-11-25T00:49:15+09:00
Subject: Re: Other ORMs [was: rails is awesome]

* Francis Hwang <sera@fhwang.net> [1112 15:12]:
> 
> On Nov 24, 2004, at 10:01 AM, Dick Davies wrote:
> 
> >* Austin Ziegler <halostatue@gmail.com> [1142 14:42]:
> >
> >>In practice, with a putative Oracle connector to AR, AR simply won't
> >>work, because Oracle's metadata tables always return the data in
> >>uppercase -- unless the table name is quoted.
> >>
> >>MySQL is a bad model -- it doesn't actually do much of anything 
> >>right.\
> >
> >And you just found this out?
> >Have you been living in a cave for the last 5 years? :)
> >
> >As a postgresql advocate (I started with pgsql over mysql because
> >	a) I wanted to learn SQL, not mySQL
> >	b) in those days mysql had a *lot* of missing features
> >	c) I'm perverse when it comes to choosing the underdog
> >)
> >
> 
> Other than the wonky SQL-MySQL compliance divide, are there specific 
> features that you can get out of PostgreSQL, or are a lot easier to use 
> in PostgreSQL, that might encourage a MySQL user like myself to change? 
> I've seriously considered switching to PostgreSQL 'cause it has a good 
> rep with people I trust, but every time I try to Google this topic I 
> never find something that convinces me to switch.

I'm afraid I don't know mySQL that well, so I'm not really the best to
answer :)

I've heard a lot of horror stories about missing features of mysql tha
I assume must have been fixed by now. See Google.

Online comparisons are about as objective as 'islam or judaism?' threads, 
and far be it from me to break tradition, so here's my 2 euro:

When I made the effort to move my postgresql stuff over to mysql
the main sore thumbs that really annoyed me were (and I don't do any
clever db stuff, this is a few just simple tables. You think my ruby
sucks? you should see my SQL)		 :

* having to define a particular table type to get certain features. 
* the syntax on simple stuff like 'create table' is just wrong :)
* mysql-over-ssl needs my.cnf tweaking - libpq handles it transparently
* mysql does'nt support external (pam) auth (that might sound perverse,
  but with postgres users can have the same password for the db as they
	do for imap/ssh/subversion/etc)
* ssl support in php-mysql isn't there. at all. I had to run 2 stunnels,
	one on either end, to get my webserver talking securely to my db. Despite
	mysqld having SSL support (startTLS, see). Sweet zombie Jesus. And 
  this appears to be the 'official' way of doing it??

Gimme a G. Gimme an R. Gimme an R.....

-- 
Rasputin :: Jack of All Trades - Master of Nuns