Re: Table Relationships

From: Curtis Scheer <Curtis(at)DAYCOS(dot)com>
To: Aaron Bono <postgresql(at)aranya(dot)com>, "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Table Relationships
Date: 2006-10-31 22:04:10
Message-ID: 031936836C46D611BB1B00508BE7345D04C02FAE@gatekeeper.daycos.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Thanks for the help.

_____

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

On 10/31/06, A. Kretschmer <andreas(dot)kretschmer(at)schollglas(dot)com
<mailto:andreas(dot)kretschmer(at)schollglas(dot)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>
==================================================================

Browse pgsql-sql by date

  From Date Subject
Next Message roopa perumalraja 2006-11-01 03:54:40 Re: Add calculated fields from one table to other table
Previous Message Volkan YAZICI 2006-10-31 21:58:08 Re: record datatype comparisons