Re: Re: [PATCHES] Select parser at runtime - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [PATCHES] Select parser at runtime
Date
Msg-id 17301.997575846@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Select parser at runtime  (Ian Lance Taylor <ian@airs.com>)
Responses Re: Re: [PATCHES] Select parser at runtime
List pgsql-hackers
Ian Lance Taylor <ian@airs.com> writes:
> For example: the datatypes have different names; the set of reserved
> words is different; Oracle uses a weird syntax for outer joins.

Is it really possible to fix these things strictly in the parser
(ie, without any semantic analysis)?  For example, I don't quite see
how you're going to translate Oracle-style outer joins to SQL standard
style without figuring out which fields belong to which relations.
Keep in mind the cardinal rule for the parsing step: Thou Shalt Not
Do Any Database Access (because the parser must work even in
transaction-aborted state, else how do we recognize ROLLBACK command?)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PATCHES] Select parser at runtime
Next
From: Tatsuo Ishii
Date:
Subject: Re: PL/pgSQL bug?