"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> Like I said, sometimes the user doesn't have a choice. Sure, it's easy to
> tell someone that has a 300-line PHP application to fix their code, but I've
> worked with people who have hundreds of thousands of lines of code and they
> don't just say, "gee, let's just search-and-replace everything!"; that's a
> testing nightmare.
To be blunt, those people aren't going to be moving to Postgres anyhow.
If the notion of fixing this issue daunts them, they are not going to be
willing to deal with the other incompatibilities between Oracle and PG.
And we are *not* buying into the notion of becoming a bug-compatible
(If EnterpriseDB wants to try to do that, fine; they'll be earning their
money the old-fashioned way...)
regards, tom lane
In response to
pgsql-patches by date
|Next:||From: Mark Kirkwood||Date: 2006-03-08 04:47:50|
|Subject: Re: pg_freespacemap question|
|Previous:||From: Tom Lane||Date: 2006-03-08 03:25:33|
|Subject: Re: variance aggregates per SQL:2003 |