Skip site navigation (1) Skip section navigation (2)

Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST)

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST)
Date: 2000-03-07 23:25:49
Message-ID: 200003072325.SAA27922@candle.pha.pa.us (view raw or flat)
Thread:
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(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

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2000-03-07 23:35:35
Subject: Re: [HACKERS] DROP TABLE inside a transaction block
Previous:From: Bruce MomjianDate: 2000-03-07 23:24:21
Subject: Re: [BUGS] grant/revoke bug with delete/update

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group