Received: from femail40.sdc1.sfba.home.com (femail40.sdc1.sfba.home.com [24.254.60.34]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8O2pvh80078 for ; Sun, 23 Sep 2001 22:51:57 -0400 (EDT) (envelope-from kway@overtone.org) Received: from bean.overtone.org ([24.249.254.100]) by femail40.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010924025152.YZCM16255.femail40.sdc1.sfba.home.com@bean.overtone.org>; Sun, 23 Sep 2001 19:51:52 -0700 Received: by bean.overtone.org (Postfix, from userid 1001) id CACC95B4B8; Mon, 24 Sep 2001 02:51:50 +0000 (GMT) Date: Mon, 24 Sep 2001 02:51:50 +0000 From: Kevin Way To: Kovacs Baldvin Cc: pgsql-sql@postgresql.org Subject: Re: Bug?: Update on ancestor for a row of a child Message-ID: <20010924025150.A6840@bean.overtone.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kb136@hszk.bme.hu on Mon, Sep 24, 2001 at 01:55:38AM +0200 X-Archive-Number: 200109/200 X-Sequence-Number: 4882 > 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