From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump and ANSI types (TODO item) |
Date: | 2000-08-05 00:21:21 |
Message-ID: | 3.0.5.32.20000805102121.01d95330@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 23:59 4/08/00 +0200, Peter Eisentraut wrote:
>>
>> Do we already have a function to represent PG types as ANSI standard types?
>
>format_type(pg_type.oid, pg_attribute.atttypmod)
Good; I thought that might be why you sent me the info...
>
>I wrote format_type for exactly this purpose a few weeks ago, but I
>figured I let you get the glory for making pg_dump use it. :-) psql uses
>it as well.
>
Is it in 7.0.2?
>Note: IMO it should not be an *option* to use format_type, it should
>always be used. It's nice for encapsulation on the programming side and
>there's no reason for using any other type names.
Sounds good to me, as long as we can be sure that the backend will
undestand it's output...one reason for making it an option is was to allow
ISO SQL exports for porting to other DBs when we know we have different
formats (but no examples spring to mind).
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2000-08-05 02:20:20 | Re: Installation Report for powerpc-apple-netbsdelf1.5 |
Previous Message | Philip Warner | 2000-08-05 00:16:17 | Re: Security choices... |