Re: how to set more than two attributes as primary keys in a table

On Mon, Dec 29, 2003 at 10:35:54 -0500,
  Casey Allen Shobe <cshobe@softhome.net> wrote:
> Bruno Wolff III (Sunday 28 December 2003 23:24)
> >   primary key (Region_Num, Num_Players)
>
> You might also find unique () to be very helpful.  I personally prefer to
> always have an id column as the primary key in any table, and to further
> constrain the table with unique's, where necessary.
>
> create table foobar (
>     id    bigint default nextval(foobar_seq),
>     foo    varchar(32),
>     bar    smallint,
>     foob    text,
>     primary key (id),
>     unique (foo, bar)
> );

Note that isn't quite the same unless you add NOT NULL constraints for
foo and bar.