| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Sally Sally <dedeb17(at)hotmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: primary key and existing unique fields |
| Date: | 2004-10-26 18:50:27 |
| Message-ID: | 417E9C73.6000503@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sally Sally wrote:
> Can you please elaborate on the point you just made as to why the
> primary key should not relate to the data (even for a case when there is
> an existing unique field that can be used to identify the record)
>
Here is a good article on the topic:
http://www.devx.com/ibm/Article/20702
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of PostgreSQL Replication, and plPHP.
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
| Attachment | Content-Type | Size |
|---|---|---|
| jd.vcf | text/x-vcard | 640 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Együd Csaba (Freemail) | 2004-10-26 18:51:31 | Re: Error restoring bytea from dump |
| Previous Message | Kevin Barnard | 2004-10-26 18:32:25 | Re: what could cause inserts getting queued up and db locking?? |