RE: Strange Type Mismatch on Insert

From: Jeff Eckermann <jeckermann(at)verio(dot)net>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: RE: Strange Type Mismatch on Insert
Date: 2001-03-20 15:27:17
Message-ID: 08CD1781F85AD4118E0800A0C9B8580B0949B0@NEZU
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Monday, March 19, 2001 6:27 PM
> To: Jeff Eckermann
> Cc: 'pgsql-general(at)postgresql(dot)org'
> Subject: Re: [GENERAL] Strange Type Mismatch on Insert
>
> Jeff Eckermann <jeckermann(at)verio(dot)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

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-03-20 15:38:24 Re: Re : overriding default value in inherited column (+ set_value function)
Previous Message Vladislav Breus 2001-03-20 15:13:57 grant under SQL92