Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 2C8D6475C5F for ; Thu, 17 Oct 2002 11:34:51 -0400 (EDT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 26AA0475D01 for ; Thu, 17 Oct 2002 11:34:47 -0400 (EDT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id BC6EED61D; Thu, 17 Oct 2002 08:34:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id A1F5F5C02; Thu, 17 Oct 2002 08:34:51 -0700 (PDT) Date: Thu, 17 Oct 2002 08:34:51 -0700 (PDT) From: Stephan Szabo To: Charles Hauser Cc: , Subject: Re: Use of reference table ('look-up-table') and FK constraint In-Reply-To: <1034863604.1760.15.camel@pandorina.biology.duke.edu> Message-ID: <20021017083401.Y9470-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/195 X-Sequence-Number: 9912 On 17 Oct 2002, Charles Hauser wrote: > Josh & Stephan, > > This helps a lot - thanks! > > Any idea what datatype 'Identifier_type IDENTITY' specifies? I don't > see this in the postgres documentation. I'll see what I can find in > sybase lingo. As a rough guess, I'd say probably a serial column, "phone_id serial primary key" is likely.