I think you may be running into the now fixed (for 7.1) bug where
ADD CONSTRAINT ... FOREIGN KEY got the column ordering wrong when checking
existing data. I may be able to build a patch against 7.0.x since the
fix is relatively minor if you don't plan to upgrade when 7.1 comes out.
On Mon, 5
For a project we are working on, I have created a custom postgresql data
type which is similar to MS SQL Server's uniqueidentifier data type. It uses
dynamic link library extension that calls the FreeDCE library to generate
GUIDs. Support for the data type and support functions is added to a
Post