From: | "Dan Wilson" <dan_wilson(at)geocities(dot)com> |
---|---|
To: | "pgsql general" <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] pg-dump -- primary Key |
Date: | 1999-07-26 02:30:53 |
Message-ID: | 004f01bed710$efbf68e0$ac0bfea9@dwilson |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I understand this, but does it set the indisprimary flag in the pg_index
table? The reason I ask is because I am writing a web based app to
administer a pgsql database and am attempting to keep track of the
indices/keys.
This is the property I am looking at determine whether the index is a
primary key. Is there a better property or flag to examine for this
purpose?
-Dan
> On Sun, Jul 25, 1999 at 03:13:39PM +1000, Chris Bitmead wrote:
> > Dan Wilson wrote:
> >
> > > Yes, I am aware that the primary key does not really mean anything
except
> > > implicitly making it a unique key, but it's supposed to be there for
> > > compatibility and it's not even in the dump.
> >
> > Someone mentioned recently that primary key enforces nulls as unique
> > whereas unique index doesn't.
> >
>
> Actually, I belive it enforces NOT NULL on primary keys, which it also
> dumps in the pg_dump output.
>
> Ross
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Wilson | 1999-07-26 05:16:52 | escaping wildcard chars |
Previous Message | Mike Mascari | 1999-07-25 22:22:49 | Re: [GENERAL] speeding up INTERSECT/EXCEPT |