From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Beta for 4:30AST ... ? |
Date: | 2000-02-28 14:46:10 |
Message-ID: | 25204.951749170@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>> It seems that allowing something like
>> bit\ varying
>> in the bootstrap scanner will solve the problem where it's being caused.
>> Internal type names should go away, not accumulate. ;)
> I'm not sure that I agree that multi-word character types are required
> internally. Somehow that seems to just push the problem of
> SQL92-specific syntax to another part of the code.
It doesn't push it anywhere: you still have the problem that the parser
expects type names to be single tokens, not multiple tokens, and any
exceptions need to be special-cased in the grammar. We can handle that
for the few multi-word type names decreed by SQL92. But allowing
internal type names to be multi-word as well will create more headaches
in other places (even if it doesn't make the grammar ambiguous, which
it well might). I think the bootstrap scanner would just be the tip of
the iceberg...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-02-28 14:48:28 | Re: [HACKERS] Locale support broken in latest snapshots |
Previous Message | Tom Lane | 2000-02-28 14:40:01 | Re: [HACKERS] A further thought on rule string size |