db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [Derby-359]Skipping over user inserted values into GENERATED BY DEFAULT identity columns....
Date Wed, 14 Dec 2005 17:27:07 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Current problem with GENERATED BY DEFAULT is that once it generates a
value that is already present in the table, <b>NONE</b> of the future
inserts can succeed. I can understand the current insert failing when
there is a duplicate value, but preventing all future inserts (fails
because they keep generating the same value, I suppose) seems wrong.<br>
I would be happy if Derby can consume identity values even if current
insert statement fails. For this case, some insert statements may fail
when they generate a value that is already present. But subsequent
inserts should pass.<br>
Mamta Satoor wrote:
  <div>I was looking at Derby-359 and was wondering what was the exact
scope of this bug. Are we saying that when system generates a value for
GENERATED BY DEFAULT column, it should check if the next value it plans
to insert is already used and if yes, then it should skip that value
and try to use the next value and continue this until it finds an
unused value for the column?

View raw message