Travis Camechis <[email protected]> writes:
> Was the original Postgres plan to keep both the Oracle Schema and the
> postgres schema requiring any new changes to the schema to be done in both
> places? That would seem to be a testing/dev nightmare.
Yup. There was a fair amount of work on a schema generation tool
("chameleon") that would let both schemas be generated from a common
source, but I'm not sure that ever got to the 100% stage. In any case
it was ignoring the elephant in the room, namely the thousands of lines
of PL/SQL code that could not by any stretch of the imagination be
handled that way. There was also a good deal of work (some of it done
by me) on doing a manual translation of that code to plpgsql, and as of
sometime last year we had a complete though largely untested
translation. But I never heard a credible proposal for keeping those
two code bases in sync, and I'm sure by now the plpgsql version has
bitrotted from failure to track subsequent changes in the PL/SQL code.
regards, tom lane
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
