The following bug has been logged online:
Bug reference: 3780
Logged by: Ning Li
Email address: [EMAIL PROTECTED]
PostgreSQL version: PostgreSQL 8.3
Operating system: Windows XP
Description:Error message happen when Starting Services
Details:
I have PostgreSQL 8.0 i
Laurent HERVE wrote:
ok thank you... and sorry for not having checked enough time in the
documentation.
anyway, i think a kind of JOIN ... USING (primary key columns) could be
useful.
if you change a primary key, because of design choice, you won't have to
rewrite all rules and views for example,
ok thank you... and sorry for not having checked enough time in the
documentation.
anyway, i think a kind of JOIN ... USING (primary key columns) could be
useful.
if you change a primary key, because of design choice, you won't have to
rewrite all rules and views for example, just simple execute wo
Please keep the list CC'd.
Laurent HERVE wrote:
in fact, i don't know why the column "code_document" is used because it
is not in the primary key of the tables.
So as this column is nullable, it gives unexpected results.
I thought only the columns on the primary key are taken into account
when
Laurent HERVE wrote:
The join is correctly done when i do not use the numero_releve='2006-10'
filter. But when i use it, the join is not working. The explain plan gives
me a information about why :
"Index Scan using document_operation_fk_idx"
but for me it seems like a bug ...
I don't see anyth
The following bug has been logged online:
Bug reference: 3778
Logged by: Laurent HERVE
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: i486-pc-linux-gnu, compiled by GCC cc (GCC) 4.1.2
(Ubuntu 4.1.2-0ubuntu4)
Description:Natural join with
