"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.
Tom Lane writes:
> [EMAIL PROTECTED] writes:
> > Postgresql itself seems to never include along with
> > , otherwise it would suffer from the same problem
>
> That's hard to believe; I think it's Qt that's doing something strange
> here.
Yeah, like compiling with thread support. ;-)
> Anyone o
[EMAIL PROTECTED] writes:
> Postgresql itself seems to never include along with
> , otherwise it would suffer from the same problem
That's hard to believe; I think it's Qt that's doing something strange
here. Still, the ANSI C standard does discourage what we are doing:
... It is unsp
"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
Your name : Frank van Vugt
Your email address : [EMAIL PROTECTED]
(with thanks to Dimitri@TrollTech for his insight & examples)
System Configuration
-
Architecture :
Intel Pentium III
Operating System :
Linux 2.4.19 with g
Piotr Kuczynski ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
Inaccurate in PostgreSQL 7.3b2 Developer's Guide
Long Description
There is small inaccurate in the "PostgreSQL 7.3b2 Developer's Guide":
[Chapter 10. Native Langu
