Thomas Lockhart wrote: > > Well in the renumbering case, the client needs to know about missing attnos > > and it has to know to ignore negative attnos (which it probably does > > already). ie. psql and pg_dump wouldn't have to be modified in that case. > > In the isdropped case, the client needs to know to exclude any column with > > 'attisdropped' set to true. > > So in both cases, the client needs to be updated. > > How about defining a view (or views) which hides these details? Perhaps > a view which is also defined in SQL99 as one of the information_schema > views which we might like to have anyway?
We could change pg_attribute to another name, and create a view called pg_attribute that never returned isdropped columns to the client. That would allow clients to work cleanly, and the server to work cleanly. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
