Re: Re: [PATCHES] Select parser at runtime

From: Ian Lance Taylor <ian(at)airs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [PATCHES] Select parser at runtime
Date: 2001-08-12 06:27:28
Message-ID: si66btyer3.fsf@daffy.airs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Ian Lance Taylor <ian(at)airs(dot)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?)

I admit that I haven't sorted out the outer join thing yet. The
others are easy enough.

Ian

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ian Lance Taylor 2001-08-12 06:31:39 Re: [PATCHES] Select parser at runtime
Previous Message Bruce Momjian 2001-08-12 04:25:28 Re: Re: [PATCHES] Select parser at runtime

Browse pgsql-patches by date

  From Date Subject
Next Message Ian Lance Taylor 2001-08-12 06:31:39 Re: [PATCHES] Select parser at runtime
Previous Message Joe Conway 2001-08-12 06:27:24 Re: bytea_ops