Re: Status on 7.0

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Jan Wieck <jwieck(at)debis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Status on 7.0
Date: 2000-01-19 15:40:11
Message-ID: 3885DADB.F529766C@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-19 15:50:20 Re: [HACKERS] Daily regression testing via vmware - useful?
Previous Message Tom Lane 2000-01-19 15:35:18 Should cast to CHAR or NUMERIC enforce default length limit?