Tom Lane <[EMAIL PROTECTED]> writes:
> Sounds like both your database and your DBA are dinosaurs ;-).
Yes.
> If you can't get your DBA to update from Oracle 8 to modern Oracle,
> you've got zip chance of persuading him to deal with Postgres,
Postgres is for use with an extern customer, so the c
Csaba Nagy <[EMAIL PROTECTED]> writes:
> both postgres and Oracle, and I have to say it took quite some time
> and a few nasty surprises until everything was stable
Thank you very much for your comments.
--
Until the next mail...,
Stefan.
pgpV8KsgMY9JV.pgp
Description: PGP signature
On Wed, 2006-04-05 at 12:19 -0400, Neil Conway wrote:
> On Wed, 2006-04-05 at 14:46 +0200, Stefan Nobis wrote:
> > Is there any way (or working solution) to extend PostgreSQL to accept
> > Oracles outer join syntax with '(+)'?
>
> Not AFAIK, and there are no plans to add support that I'm aware of.
On Wed, 2006-04-05 at 14:46 +0200, Stefan Nobis wrote:
> Is there any way (or working solution) to extend PostgreSQL to accept
> Oracles outer join syntax with '(+)'?
Not AFAIK, and there are no plans to add support that I'm aware of.
EnterpriseDB claim to have pretty good Oracle compatibility, so
Stefan Nobis <[EMAIL PROTECTED]> writes:
> [ still on Oracle8 ]
> BTW: You have to use the cost based optimizer (new syntax with rule
> based optimizer yields really bad performance). And our DBA really
> don't like statistics... :(
Sounds like both your database and your DBA are dinosaurs ;-).
I
> BTW: You have to use the cost based optimizer (new syntax with rule
> based optimizer yields really bad performance). And our DBA really
> don't like statistics... :(
This is kind of off topic on this list, but there are ways to force
Oracle to use specific plans by carefully hinting it.
And th
> Because there are tons of legacy code I'd have to convert and until
> now the Oracle server is still Oracle8. :(
I would think that patching postgres will be no less challenging than
fixing the legacy code... unless you really have a few tons of it or you
simply can't do it (no access for e.g.).
Csaba Nagy <[EMAIL PROTECTED]> writes:
> Why would you do that ? If you need a solution which works both on
> postgres and oracle, use the standard outer join syntax supported by
> postgres - it is supported by the latest oracle versions too.
BTW: You have to use the cost based optimizer (new syn
Csaba Nagy <[EMAIL PROTECTED]> writes:
> Why would you do that ? If you need a solution which works both on
> postgres and oracle, use the standard outer join syntax supported by
> postgres - it is supported by the latest oracle versions too.
Because there are tons of legacy code I'd have to conv
Stefan,
Why would you do that ? If you need a solution which works both on
postgres and oracle, use the standard outer join syntax supported by
postgres - it is supported by the latest oracle versions too.
We do this here successfully...
Cheers,
Csaba.
On Wed, 2006-04-05 at 14:46, Stefan Nobis
10 matches
Mail list logo
