NYCPHP Meetup

[Kenneth Downs]

Anthony Wlodarski wrote:
> We use PostgreSQL for our environments.  Although it is quite powerful there
> are some ease of use issues with tuning and getting it to perform at its
> maximum.  But the great thing about PostgreSQL is transactions right out of
> the box, that has been the most useful feature so far.
>
> I haven't had a chance to play with Oracle but I don't see them GPL'ing that
> DB any time soon.  Clients pay too much to use it.
>   

I've been experimenting with some cross-platform features in the past 
few weeks, and I found myself surprised that PostgreSQL is a lot more 
powerful and flexible than I had realized, even though I've used it 
almost exclusively for the past 4-5 years.

I was digging through the specs for MS SQL Server, and was surprised to 
find out how limited their triggers still are.  I sort of figured they 
would have rocketed forward since last I used the product.

Oracle seems to be the only contender for Postgres's overall power and 
flexibility (and here come the flames from those who say I put that 
backwards).

MySQL still has a lot of growing up to do:

1) Triggers cannot see the value of auto_increment columns
2) Triggers cannot write to the tables being affected
3) Triggers do not fire on delete cascade ???!!!?? WTF??
4) Insert undiscovered limitation here :)

But to their credit, they do have "INSTEAD OF" triggers on views, a very 
grown up feature.

There is still a soft spot in my heart for DB/2, since I got to code for 
it on the AS/400 years ago, it is also quite powerful and can be bent to 
your will with a little patience.

> -Anthony
>
> On Wed, May 6, 2009 at 8:13 PM, David Krings <ramons at gmx.net> wrote:
>
>   
>> Jesse Callaway wrote:
>>
>>     
>>> I think the idea is that MySQL had a decent business model and was
>>> doing quite well. If Oracle does decide to shitcan it, it's GPL'd
>>> anyway and will live on kinda like CentOS does.
>>>
>>>
>>>       
>> Besides that MySQL forked already and while I do like and use MySQL, there
>> is still PostgreSQL (did I write that correctly, people always go bonkers
>> when I write it wrong) and plenty of other options. Unless one has MySQL
>> specific code (which would be a bad thing anyway) swapping out database
>> engines should be fairly easy. Nice thing is that PHP supports pretty much
>> any database engine out there.
>>
>> David
>>
>> _______________________________________________
>> New York PHP User Group Community Talk Mailing List
>> http://lists.nyphp.org/mailman/listinfo/talk
>>
>> http://www.nyphp.org/show_participation.php
>>
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/show_participation.php


-- 
Kenneth Downs
Secure Data Software
ken at secdat.com  www.andromeda-project.org www.secdat.com
Office: 631-689-7200
Cell: 631-379-0010
Fax: 631-689-0527

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20090506/9913f692/attachment.html>