"Mathew Frank" <[EMAIL PROTECTED]> writes:
> I'm always a bit nervous about calling anything a bug... 9/10 is caused by a
> typo or something on behalf of the user ;)
Well, it's a two-way street: typos and other sorts of mistakes tend to
stress paths that the developers would've never thought to
> which appears correct (you misspelled the column name).
>
> 7.2 does foreign key validity checking in a funny order that causes it
> to produce the other error message first. While not incorrect, it's
> sure misleading :-(
Thanks a bunch.
I'm always a bit nervous about calling anything a bug.
"Mathew Frank" <[EMAIL PROTECTED]> writes:
> UNIQUE constraint matching given keys for referenced table "price_lists" not
> found
As of CVS tip your example gives
ERROR: ALTER TABLE: column "s_price_list_id" referenced in foreign key constraint
does not exist
which appears correct (you misspe
Hello people,
I'm a newbie to this list (though I've been hanging around on the ODBC list
for some time and I've been working with pgSQL for about 8months) so go
easy? ;-)
I realise this error is to stop a bad foreign key reference being created.
However I have a table with a multi-column primary
