RE: Strange Type Mismatch on Insert - Mailing list pgsql-general

From Jeff Eckermann
Subject RE: Strange Type Mismatch on Insert
Date
Msg-id 08CD1781F85AD4118E0800A0C9B8580B0949B0@NEZU
Whole thread Raw
In response to Strange Type Mismatch on Insert  (Jeff Eckermann <jeckermann@verio.net>)
List pgsql-general
Absolutely right.  I've been editing my setup script, and a mistake crept
in.  Obvious in retrospect, but then this is the first time I've actually
used referential integrity features...
Thanks for saving my sanity yet again!

> -----Original Message-----
> From:    Tom Lane [SMTP:tgl@sss.pgh.pa.us]
> Sent:    Monday, March 19, 2001 6:27 PM
> To:    Jeff Eckermann
> Cc:    'pgsql-general@postgresql.org'
> Subject:    Re: [GENERAL] Strange Type Mismatch on Insert
>
> Jeff Eckermann <jeckermann@verio.net> writes:
> > Can anyone see what is the problem with the following insert?
> > gmp=# insert into data (site, gmp_id, item, category, gmp) values
> > ('Rochester', 22, 'Design fee', 12, 40000.00);
> > ERROR:  Unable to identify an operator '=' for types 'text' and 'int4'
>
> Got any foreign keys associated with that table?  Check for type
> mismatch between referencing and referenced columns.  It's a bug
> that such problems are not detected when you declare the key
> relationship, but right now they're not detected until runtime...
>
>             regards, tom lane

pgsql-general by date:

Previous
From: Nico
Date:
Subject: Re : overriding default value in inherited column (+ set_value function)
Next
From: Tom Lane
Date:
Subject: Re: Re : overriding default value in inherited column (+ set_value function)