| From: | Brandon Metcalf <brandon(at)geronimoalloys(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | simulate multiple primary keys |
| Date: | 2009-07-02 17:27:48 |
| Message-ID: | Pine.LNX.4.58L.0907021223180.6476@cedar.geronimoalloys.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I have the following table:
gms=> \d jobclock
Table "public.jobclock"
Column | Type | Modifiers
-------------+--------------------------------+----------------------------------------------------------------
jobclock_id | integer | not null default nextval('jobclock_jobclock_id_seq'::regclass)
employee_id | integer | not null
machine_id | character varying(4) | not null
workorder | character varying(8) | not null
operation | integer | not null
bartype | character varying(10) | not null
clockin | timestamp(0) without time zone | not null
clockout | timestamp(0) without time zone | default NULL::timestamp without time zone
comments | character varying(255) | default NULL::character varying
Indexes:
"jobclock_pkey" PRIMARY KEY, btree (jobclock_id)
...
I need to keep jobclock_id unique and not null, but I also need to
ensure that no row is duplicated. Is my best bet to drop the current
primary key and make a primary key out of the columns that I want to
ensure remain unique from row to row?
Thanks.
--
Brandon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hartman, Matthew | 2009-07-02 17:29:10 | Re: simulate multiple primary keys |
| Previous Message | James B. Byrne | 2009-07-02 16:56:09 | PG_DUMP/RESTORE Would like an explanation of these (non-critical) errors |