db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: Confusing message from constraint processing (DERBY-4248)
Date Fri, 19 Jun 2009 09:14:14 GMT
Bryan Pendleton <bpendleton@amberpoint.com> writes:

> While working with Eranda on DERBY-4248, we've run across a behavior
> I don't understand, and I am hoping somebody can shed some light on it.
> Below is a very short program, and the result I get when I run it.
> Note that the table name ("C1") and the cursor name ("C1") are the
> same, and somehow this seems to confuse the constraints binding code
> for the update statement into thinking that column "c2" doesn't exist
> in the table, when in fact the column *does* exist.
> Is this a bug? Or am I misunderstanding what the behavior should be?

Hi Bryan,

It looks like a bug to me. It also seems like the name of the cursor is
not relevant, as it fails the same way for me even if I change it to
something completely different (like MYCURSOR).

Knut Anders

View raw message