The following bug has been logged online:
Bug reference: 5505
Logged by: Tommy McDaniel
Email address: tommst...@myway.com
PostgreSQL version: 8.4.4
Operating system: Kubuntu 9.10
Description:Busted referential integrity with triggers
Details:
Let us create a table
The following bug has been logged online:
Bug reference: 5506
Logged by: Fernando Cano
Email address: fc...@uniovi.es
PostgreSQL version: 8.4
Operating system: Ubuntu 9.04
Description:Error in the grammar of de joins
Details:
This sentences are valid with your gramm
The following bug has been logged online:
Bug reference: 5507
Logged by: Shinji Nakajima
Email address: sina...@jops.co.jp
PostgreSQL version: 8.3.8
Operating system: Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Description:missing chunk number 0 for toast va
"Tommy McDaniel" writes:
> Let us also create a trigger to disable UPDATEs on table_2:
> ...
> And, we have now broken referential integrity.
Yup, this is not a bug, it's a feature. Triggers fire on
referential-integrity updates. (If they didn't, you could not for
example have a logging trigger
"Fernando Cano" writes:
> This sentences are valid with your grammar but generate an error.
> create table t1 ( id_t1 smallint, name text);
> create table t2 ( id_t2 smallint, name text);
> select * from natural join using (id) ;
> select * from t1 natural cross join t2;
> select * from natural
"Shinji Nakajima" writes:
> Error message called "missing chunk number" occurred when I did select of
> the specific column of the specific table.
This might indicate that the toast table's index was corrupted.
> I delete a record, and the system restores, but prime cause is unknown.
> Will this
"Shinji Nakajima" wrote:
> Error message called "missing chunk number" occurred when I did
> select of the specific column of the specific table.
> I delete a record, and the system restores, but prime cause is
> unknown. Will this be a bug of the databases?
Errors like this are usually cau
On Mon, Jun 14, 2010 at 11:28 AM, Shinji Nakajima wrote:
> PostgreSQL version: 8.3.8
> Description: missing chunk number 0 for toast value X in
> pg_toast_X
>
> I delete a record, and the system restores, but prime cause is unknown.
> Will this be a bug of the databases?
Probably.
I can understand firing the triggers. But what's up with not checking that the
foreign key constraint is met? If the user has to manually ensure that values
maintain referential integrity, why have foreign keys at all? The whole point
of foreign keys is to make the database ensure referential in
"Tommy McDaniel" writes:
> I can understand firing the triggers. But what's up with not checking that
> the foreign key constraint is met? If the user has to manually ensure that
> values maintain referential integrity, why have foreign keys at all? The
> whole point of foreign keys is to make
10 matches
Mail list logo
