Peter Eisentraut <peter_e@gmx.net> writes:
> I'm not sure whether I like the notion of having to maintain multiple
> parsers in the future. We have always been quite fair in accepting
> extensions and aliases for compatibility, so I don't see a problem there.
> Then again, we're implemented an SQL server, not an Oracle server. If you
> want to convert your application there's this ora2pg thing.
An approach such as ora2pg solves a specific problem. It doesn't
really solve the general problem of people familiar with Oracle who
want to use Postgres. It doesn't at all solve my problem, which is to
have an application which can easily speak to either Oracle or
Postgres.
> > For example: the datatypes have different names; the set of reserved
> > words is different;
>
> Unless you have implemented a different parsing algorithm or want to rip
> out features you're going to have a hard time changing the set of reserved
> words.
That's why I'm implementing a different parsing algorithm.
Ian