Hello.

2:being able to disable the "identity" feature for a column
3:being able to generate a column as non identity and after data is
populated, alter table to add the "identity" to the column

I think those are needed to allow user to enable loading data "AND" keep values at identity column tidy.
(Now "tidy" means user can't decide pk value at their discretion.)


We should have both approaches after all ...

Then I think this is matter of priority.

/*

        Tomohito Nakayama
        [EMAIL PROTECTED]
        [EMAIL PROTECTED]

        Naka
        http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/
----- Original Message ----- From: "Kathey Marsden" <[EMAIL PROTECTED]>
To: "Derby Development" <[email protected]>
Sent: Sunday, April 03, 2005 11:12 PM
Subject: Re: (Derby 167) was Re: [Patch] Re: About improvement of DERBY-134



TomohitoNakayama wrote:

Hello.

I was interested in issue of Derby-167...

I recognized there was proposed three options.
1:being able to "generate by default as identity"
2:being able to disable the "identity" feature for a column
3:being able to generate a column as non identity and after data is
populated, alter table to add the "identity" to the column

In my opinion , option 2 and option 3  increase statuses which table
can take , identity feature working state and not working state,
so they would make it complex to maintain db.
On the other hand, if we take option 1, we need to prevent it from to
have same value in identity column.

I think it's ok to let the user prevent duplicates  with a primary key
if they want to.
When creating the table,  the user would need to make sure that they
used START WITH  to ensure that generation starts with the maximum value
+ 1.  I put a comment in the bug with how I think the process would go.

A bit precarious I know if you forget to create your table properly, but
at least it makes it *possible* to load data.
Later we could enhance support for ALTER TABLE to alter the identity
column specification to specify a RESTART WITH value.

Thanks


Kathey







--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.1 - Release Date: 2005/04/01




-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.2 - Release Date: 2005/04/05



Reply via email to