| From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | Webb Sprague <wsprague100(at)yahoo(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Create Primary Key? |
| Date: | 2000-08-30 11:42:48 |
| Message-ID: | m13U6GW-000AWSC@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Thus spake Stephan Szabo
> We don't currently support the SQL syntax for adding
> a PK to a table. However, if you have the columns
> as NOT NULL already, adding a unique index to the
> columns in question has the same general effect.
Except for interfaces such as PyGreSQL that recognize the primary key
and use it.
> > Is there syntax to create a primary key after the
> > table has been defined and populated? I think I could
> > speed things up quite a bit by not having any indexes
> > at all when I do my mass copies.
Why not just use the copy function? That's what it's for.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2000-08-30 14:52:07 | Re: Create Primary Key? |
| Previous Message | Webb Sprague | 2000-08-30 03:52:15 | Re: Create Primary Key + Massive Copy's? |