I learned MySQL then went on to Postgres. I chose postgres for my in
house project just because of the row locking and transactions. Looking
back I could have used MySQL. I have yet to use stored procedures or
many of the high level functions of Postgres however transactions make
things so much cleaner. I do not think MySQL is a bad system. It works
well for many people in many situations. I think that MySQL and SAP
getting together could be very exciting. When it comes to SQL databases
I would say we have a wealth good choices. This if I use PHP I have to
use MySQL is a load of tripe. PHP can work just fine with Postgres. I
hate to even suggest this but has anyone thought of adding PHP to the
languages that you can use to write stored procedures in Postgres?
Roderick A. Anderson wrote:
>On 19 Aug 2003, Bo Lorentsen wrote:
>
>
>
>>Also have anyone tryed to compare the new transaction model in MySQL 4.x
>>to PostgreSQL ?
>>
>>
>
>Bo, I've recently started having to deal with MySQL. (Web sites
>wanting/using php _need/have-to-have_ MySQL. Their words not mine.) And
>from going from a "I dislike MySQL" to "I'm really hating MySQL" has been
>getting easier and easier.
> My dealings with MySQL are for the 3.xx version but I semi-followed a
>thread on this several months ago so feel fully qualified to to throw in
>my views. :-) My take on others research was that MySQL transaction
>model is a bubble gum and bailing wire add on not an integral part of
>MySQL. It _was_ tacked onto the top of the database so if either it or
>MySQL failed you were likely to loose data.
>
>
>
>>I'm looking forward to recive even more constructive arguements :-)
>>
>>
>
>How about "Friends don't let friends use MySQL"?
>
>Hopefully others with a stonger knowledge will provide this.
>
>
>Rod
>
>
