Re: Status on 7.0
Already added to TODO list.
Can I ask how our big open items for 7.0 are doing:
istm that pg_dump could benefit greatly if it translated internal
Postgres type names to the SQL92-standard names. For example, int4 ->
integer, int8 -> bigint, etc. This would be analogous to the
translation we do when parsing queries in the backend, converting
(e.g.) integer -> int4.This feature would make it a bit easier to move databases around, esp.
away from Postgres for those who have to...Anyone interested in looking at this? If not, can you add it to the
ToDo Bruce?- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
--
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 19026Import Notes
Reply to msg id not found: 3885DADB.F529766C@alumni.caltech.edu
Bruce Momjian writes:
istm that pg_dump could benefit greatly if it translated internal
Postgres type names to the SQL92-standard names. For example, int4 ->
integer, int8 -> bigint, etc. This would be analogous to the
translation we do when parsing queries in the backend, converting
(e.g.) integer -> int4.
I once proposed to create a function `format_type' or some such which
would take an internal type name and a modifier and format it to some
canonical representation. I recall that was well received and I'm still
interested in that, but I'd let the function manager changes die down
first.
--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden