Skip site navigation (1) Skip section navigation (2)

Re: pg_dumap not include foreign key...

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: xyzii <xyzii(at)kimo(dot)com(dot)tw>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dumap not include foreign key...
Date: 2000-12-29 23:15:08
Message-ID: Pine.BSF.4.21.0012291513010.19996-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-admin
You should have another lines later in the dump that start
with CREATE CONSTRAINT TRIGGER 
These are the internal representation of the foreign key
constraint and is how pg_dump[all] currently should be 
dumping those constraints out.  They probably are near
the bottom of the dump.

On Mon, 25 Dec 2000, xyzii wrote:

> me datastru ,try pg_dumpall > aa.out what not include foreign key......
> 
> CREATE TABLE "purcsub" (
>    "trn_no" char(14) NOT NULL,
>    "seq" int4 DEFAULT nextval('seq'::text),
>    "pmrc_no" varchar(14),
>    "item_no" char(20) NOT NULL,
>    "item_na1" varchar(120),
>    "color_na" varchar(20),
>    "ware_no" char(4),
>    "unit" varchar(4),
>    "trn_qty" int2,
>    "qty" float8 default 0,
>    "sqty" float8 default 0,
>    "price" float8 default 0,
>    "sprice" float8 default 0,
>    "discount" float8 default 0,
>    "amount" float8 default 0,
>    "memo" varchar(20),
>    "trn_type" varchar(2),
>    "trn_date" date,
>    "fact_no" char(20),
>    "giveaway" varchar(1),
> foreign key (trn_no) references purc (trn_no)
> ON DELETE CASCADE ON UPDATE CASCADE
> 
> );


In response to

pgsql-admin by date

Next:From: Tomaz BorstnarDate: 2000-12-29 23:22:43
Subject: Re: Is that a bug?
Previous:From: Tom LaneDate: 2000-12-29 21:03:13
Subject: Re: psql dies if I use non-default MaxBackends & NBuffers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group