From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Mike Mascari <mascarm(at)mascari(dot)com> |
Cc: | Sally Sally <dedeb17(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: primary key and existing unique fields |
Date: | 2004-10-26 20:54:43 |
Message-ID: | 417EB993.9080209@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>> Here is a good article on the topic:
>>
>> http://www.devx.com/ibm/Article/20702
>
> The surrogate key isn't solving the underlying logical inconsistency
> problem. It is being used as a work-around to cover one up. I suspect
> the author of being a MySQL user.
Actually he is a software project consultant for IEEE.org and he holds
a Ph.D. in Theoretical Physics.
Sincerely,
Joshua D. Drake
>
> Mike Mascari
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
--
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 | Mike Mascari | 2004-10-26 21:26:24 | Re: primary key and existing unique fields |
Previous Message | Karim Nassar | 2004-10-26 20:51:10 | Re: Duplicating a database |