I talked to the Orafce author. He says Orace is focused on adding
missing Oracle functionality to Postgres, rather than helping in
porting.
For example, decode() was only added in Orafce 3.0beta because Postgres
already has the CASE statement. Also, NVL is COALESCE:
http://forums.devshed.com/postgresql-help-21/does-postgresql-7-4-supports-nvl-decode-function-which-are-178892.html
For this reason, I suggest we rewrite decode() and NVL to be
ANSI-standard Postgres and Oracle supported syntax, rather than using
Orafce for these cases.
FYI, Orafce 2.1.4 works on Postgres 8.1, while 3.0.0.beta3 does not
compile. I can probably get that fixed if we want 3.0.0 for some
reason, but we might be better going with the more stable 2.1.X release.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
