db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TomohitoNakayama" <tomon...@basil.ocn.ne.jp>
Subject Re: (Derby 167) was Re: [Patch] Re: About improvement of DERBY-134
Date Sun, 03 Apr 2005 11:03:13 GMT

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.

Best regards.


         Tomohito Nakayama


----- Original Message ----- 
From: "Kathey Marsden" <kmarsdenderby@sbcglobal.net>
To: "Derby Development" <derby-dev@db.apache.org>
Sent: Sunday, April 03, 2005 12:39 AM
Subject: (Derby 167) was Re: [Patch] Re: About improvement of DERBY-134

> TomohitoNakayama wrote:
>> Hello.
>> Thank for all who advise and help me !
>> Now I'm reading code of derby here and there , and found this program
>> is very attractive.
>> I want to find next material for hacking :D
> Hello Tomohito,
> Since you are looking for a next project ,  I wanted to put a plug in
> for my personal crusade for
> Derby-167.  Inserting values in an identity column.
> http://issues.apache.org/jira/browse/DERBY-167
> I think would be tremendous value you in implementing this feature as
> currently it is not possible to import  data to Derby  if you have an
> autoincrement column and want to keep your primary keys intact.   I know
> there are others who have expressed interest and would be willing to
> help you in this project.     I don't want to get into too many details
> on this thread outside the Jira comments but just to give you an idea,
> Satheesh I think proposed a specific SQL Standard way to do this and
> Mamta promised support with reviews or whatever.
> I'd suggest  first submit a proposed solution to the community and get
> consensus before starting to implement a solution.
> I think it would be a way for you to add huge value to Derby.
> Thanks
> Kathey
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.8.6 - Release Date: 2005/03/30

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

View raw message