Re: Bug with dump/restore when using UNION and ORDER BY in views

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Bug with dump/restore when using UNION and ORDER BY in views
Date: 2002-08-04 05:24:00
Message-ID: 00a801c23b77$24bd2dc0$0200a8c0@SOL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> Yeah. This is fixed in current sources, and I back-patched it into
> the REL7_2 branch, but current plans don't seem to include a 7.2.2
> release --- we'll be going straight to 7.3 beta instead.

Is it worth doing a 7.2.2 patch that will dump people's foreign keys as
ALTER TABLE/ADD FOREIGN KEY instead of a bunch of CREATE CONSTRAINT
TRIGGERs, so that they actually become constraints in 7.3?

Also Tom - did you check if you can CREATE CONSTRAINT TRIGGER on a dropped
column - I think I neglected to look at that in the patch I submitted
originally.

Chris

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2002-08-04 05:30:37 Re: Bug with dump/restore when using UNION and ORDER BY in views
Previous Message Tom Lane 2002-08-04 03:06:41 Re: Bug with dump/restore when using UNION and ORDER BY in views