From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST) |
Date: | 2000-03-07 06:58:22 |
Message-ID: | 19134.952412302@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> In turn I'm thinking that it might be nice to have a backend function like
> format_type(name[, int4]) that formats an internal type and any size
> modifier for client consumption, like
> format_type('varchar', 8) => "CHARACTER VARYING(8)"
> format_type('my type') => "\"my type\""
> format_type('numeric', {xxx}) => "NUMERIC(9,2)"
> That could put an end to keeping track of backend implementation details
> in psql, pg_dump, and friends.
Seems like a good idea, though I think it's a bit late in the 7.0 cycle
for such a change. Maybe for 7.1?
Also, I assume you mean that the int4 arg would be the typmod value ---
your examples are not right in detail for that interpretation.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-03-07 07:53:49 | Re: [HACKERS] DROP TABLE inside a transaction block |
Previous Message | Tom Lane | 2000-03-07 06:55:21 | Re: [HACKERS] Re: [GENERAL] Version 7.0 beta problem |