Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST)
Bruce Momjian <pgman@candle.pha.pa.us>
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Lockhart <lockhart@alumni.caltech.edu>, pgsql-hackers@postgresql.org
Date: 2000-03-07T23:25:49Z
Lists: pgsql-hackers
> Okay, that's the first reasonable argument I've heard in this thread, and
> I'll buy it. Since correspondence between internal type names and function
> names *is* achievable without hacks we might as well go for this one.
>
> 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.
Great idea! psql and pg_dump can use it.
--
Bruce Momjian | http://www.op.net/~candle
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026