Re: 7.3 gotchas for applications and client libraries

Was this going to make it into the release notes or something?

Chris

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
> Sent: Tuesday, 3 September 2002 9:54 AM
> To: pgsql-hackers(at)postgresql(dot)org; pgsql-interfaces(at)postgresql(dot)org
> Subject: [HACKERS] 7.3 gotchas for applications and client libraries
>
>
> Bruce suggested that we need a porting guide to help people look for
> application and client-library code that will be broken by the changes
> in PG 7.3. Here is a first cut at documenting the issues.
> Comments welcome --- in particular, what have I missed?
>
> regards, tom lane
>
>
> Revising client-side code for PG 7.3 system catalogs
>
>
> Here are some notes about things to look out for in updating client-side
> code for PG 7.3. Almost anything that looks at the system catalogs is
> probably going to need work, if you want it to behave reasonably when you
> start using 7.3's new features such as schemas and DROP COLUMN.
>
> As an example, consider the task of listing the names and datatypes for
> a table named "foo". In the past you may have done this with a query like
>
> SELECT a.attname, format_type(a.atttypid, a.atttypmod)
> FROM pg_class c, pg_attribute a
> WHERE c.relname = 'foo'
> AND a.attnum > 0 AND a.attrelid = c.oid
> ORDER BY a.attnum

...