From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Beta for 4:30AST ... ? |
Date: | 2000-02-28 23:30:26 |
Message-ID: | 200002282330.SAA24391@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> Thomas Lockhart writes:
>
> > 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. We could just as
> > easily (?) translate *every* "xxx VARYING" to "varxxx" on input, and
> > do the inverse on output or pg_dump.
>
> On the one hand I propose what seems like editing a handful of lines in
> the bootstrap scanner (an internal interface) to solve this problem once
> and for all. What you are proposing is that every client interface (libpq,
> SPI, PL du jour, who knows) will have to know a list of the latest hacks
libpq doesn't know anything about syntax. It is mostly gram.y files. I
think ecpg is the only other one that needs the fix.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-02-29 00:04:56 | Re: [HACKERS] Re: ALTER TABLE DROP COLUMN |
Previous Message | Tom Lane | 2000-02-28 23:25:10 | Re: NOT {NULL|DEFERRABLE} (was: bug in 7.0) |