From: | "Aaron Bono" <postgresql(at)aranya(dot)com> |
---|---|
To: | "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 20:43:31 |
Message-ID: | bf05e51c0610311243u6a1c05f7n263de118da4d2037@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 10/31/06, A. Kretschmer <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://codeelixir.com
==================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2006-10-31 21:18:24 | Re: Round Numeric Type |
Previous Message | George Pavlov | 2006-10-31 20:38:36 | record datatype comparisons |