From: Kevin Way <kevin.way@overtone.org>
To: Kovacs Baldvin <kb136@hszk.bme.hu>
Cc: pgsql-sql@postgresql.org
Subject: Re: Bug?: Update on ancestor for a row of a child
Date: Mon, 24 Sep 2001 02:51:50 +0000
Message-ID: <20010924025150.A6840@bean.overtone.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0109240143280.11546-100000@ural2>
References: <Pine.GSO.4.33.0109240143280.11546-100000@ural2>
> The problem is: when updating a row in an ancestor table,
> which is really belongs to a child, there's something wrong
> with the CHECK system.
Well, I believe you found one minor problem. The bigger one is still
lurking in the shadows though. To duplicate it, take my previous schema,
and add
lastlog TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
to the users table, between pass_hash and logged_in.
After doing so, you'll find that postgres actually crashes when you try
to insert a vote into the uservote table. That's the one that has me
looking at the costs involved with migrating to Oracle.
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: kevin.way@overtone.org, kb136@hszk.bme.hu
Subject: Re: Bug?: Update on ancestor for a row of a child
In-Reply-To: <20010924025150.A6840@bean.overtone.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox