pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Curtis Scheer <Curtis@DAYCOS.com>
To: Aaron Bono <postgresql@aranya.com>
To: A. Kretschmer <andreas.kretschmer@schollglas.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Table Relationships
Date: Tue, 31 Oct 2006 16:04:10 -0600
Message-ID: <031936836C46D611BB1B00508BE7345D04C02FAE@gatekeeper.daycos.com> (raw)

Thanks for the help.

 

  _____  

From: Aaron Bono [mailto:postgresql@aranya.com] 
Sent: Tuesday, October 31, 2006 2:44 PM
To: A. Kretschmer
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Table Relationships

 

On 10/31/06, A. Kretschmer <andreas.kretschmer@schollglas.com
<mailto:andreas.kretschmer@schollglas.com> > wrote:

am  Tue, dem 31.10.2006, um 21:08:24 +0100 mailte A. Kretschmer folgendes:
> am  Tue, dem 31.10.2006, um 13:32:59 -0600 mailte Aaron Bono folgendes:
> > I would go further by adding a type table like this:
> >
> > operation_type (
> >     operation_type_id bigserial (PK),
>
> You are sure, that you need bigserial?

Hey, your idea is okay, but i think, we don't need *BIG*serial for this. 
Okay?


Andreas


Sorry, just force of habbit.  Serial works or you can just drop the id and
use the code as the primary key.  You should at the very least put a unique
constraint on the code field. 

-- 
==================================================================
   Aaron Bono
   Aranya Software Technologies, Inc.
   http://www.aranya.com <http://www.aranya.com; 
   http://codeelixir.com <http://codeelixir.com; 
================================================================== 

view thread (13+ messages)  latest in thread

Message-ID: <031936836C46D611BB1B00508BE7345D04C02FAE@gatekeeper.daycos.com>
Permalink:  ../031936836C46D611BB1B00508BE7345D04C02FAE@gatekeeper.daycos.com/
Also on:    postgresql.org/message-id/031936836C46D611BB1B00508BE7345D04C02FAE@gatekeeper.daycos.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: Curtis@DAYCOS.com, postgresql@aranya.com, andreas.kretschmer@schollglas.com
  Subject: Re: Table Relationships
  In-Reply-To: <031936836C46D611BB1B00508BE7345D04C02FAE@gatekeeper.daycos.com>
  References: <031936836C46D611BB1B00508BE7345D04C02FAE@gatekeeper.daycos.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox