Vince Vielhaber <vev@michvhf.com> writes:
> An Oracle compatibility mode wouldn't be a bad idea, but at what cost
> and at how much effort?
That is why I focused on the relatively minor changes to Postgres
required to hook in an alternate parser. I personally would not
expect the mainline Postgres team to worry about Oracle support. But
if an Oracle parser can be decoupled from the mainline of Postgres
work, then most of the cost will be paid by the people who care about
it. (Not all of the cost, because some communication will be required
when the parse tree nodes are changed.)
Along these lines, I don't think Bruce's suggestion of modifications
to the Postgres gram.y is a good idea, because it causes the Oracle
parser to add an ongoing cost to the Postgres parser.
Ian
