Re: UNIQUE constraint matching given keys for referenced

From: Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>
To: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: UNIQUE constraint matching given keys for referenced
Date: 2002-08-09 13:31:01
Message-ID: 20020809133101.98392.qmail@web20808.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ouch: end of a long day :-)

Seems kind of odd that PostgreSQL should care more
about the non-existence of the unique constraint on a
field than about the non-existence of that field
itself. Not the only place where less-than-optimal
error messages may be encountered, however.

Thanks for your help.

--- "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
wrote:
> On Thu, 8 Aug 2002, Jeff Eckermann wrote:
>
> > Thought I understood this, but evidently not...
> > couldn't find anything in the docs or archives
> that
> > helped me, either.
> >
> > Trying to add a new table, then referencing a
> number
> > of other tables to a field in the new table.
> Table
> > definition:
> >
> > create table "employee" (
> > "emp_id" integer default
> > nextval('employee_emp_id_key'::text) not null,
> > "emp_num" text,
> > ...
> > constraint "employee_pkey" primary key
> > ("emp_id"),
> > constraint "emp_num_key" unique (emp_num)
> > );
> >
> > personnel_benefits=# \i employees.dump
> > You are now connected as new user jeck.
> > psql:employees.dump:31: NOTICE: CREATE
> TABLE/PRIMARY
> > KEY will create implicit index 'employee_pkey' for
> > table 'employee'
> > psql:employees.dump:31: NOTICE: CREATE
> TABLE/UNIQUE
> > will create implicit index 'emp_num_key' for table
> > 'employee'
> > CREATE
> > personnel_benefits=# alter table emp_insurance add
> > constraint ei_emp_fk foreign key (emp_no)
> references
> > employee (emp_no);
> /\
> ||
> You've got a typo in your alter table line. Should
> be emp_num from the table
> definition you've given above.
>
>
> > NOTICE: ALTER TABLE ... ADD CONSTRAINT will
> create
> > implicit trigger(s) for FOREIGN KEY check(s)
> > ERROR: UNIQUE constraint matching given keys for
> > referenced table "employee" not found
> > personnel_benefits=#
>
> Then hopefully this error message will magically
> disappear.
>
>
> --
> Nigel J. Andrews
> Director
>
> ---
> Logictree Systems Limited
> Computer Consultants
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
majordomo(at)postgresql(dot)org

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-08-09 13:41:16 Re: The standard 'why does it take so long' question
Previous Message frbn 2002-08-09 13:11:07 Re: Warning: PostgreSQL query failed: ERROR: [my_tabel]: