>> We don't :) Why would we want to offer MySQL when we can offer
>> PostgreSQL?
>
> So...less SQL "gotchas" on PostgreSQL?
Apparently so, nobody bothered to compile a list :-)
I am not sure if there are actually less "gotchas", but in my
experience they are different: they are about performance, not
about data integrity. I feel much more comfortable with that
approach: performance issues can easily be solved with more iron
(to a certain extent of course). But if you don't know if the
data entered last year is correct, your problem is not that
easily solved.
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
