Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST)
Date
Msg-id 200003072325.SAA27922@candle.pha.pa.us
Whole thread Raw
In response to Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST)  (Peter Eisentraut <peter_e@gmx.net>)
List 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,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: [BUGS] uniqueness not always correct
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] DROP TABLE inside a transaction block