On Tue, 08 Mar 2005 15:12:25 -0800, Kathey Marsden <[EMAIL PROTECTED]> wrote: > Hello Derby Development Community, > > I think that this is one of those great opportunities for a developer > new to the Derby project to add real value to product and learn a bit > about Derby without taking on a huge project.* Is there anyone out there > willing to volunteer to propose and implement a solution? * I would be > willing to offer as much support as I can, answer questions that are > posted, vote on proposals, review submissions, etc. > > Please volunteer! > > Thanks > > Kathey > > > Christian Rodriguez (JIRA) wrote: > > >Inserting values in an identity column > >-------------------------------------- > > > > Key: DERBY-167 > > URL: http://issues.apache.org/jira/browse/DERBY-167 > > Project: Derby > > Type: Improvement > > Components: SQL > > Versions: 10.1.0.0 > > Environment: SQL > > Reporter: Christian Rodriguez > > > > > >It is not possible to insert a specific value in a column defined as > >identity. This makes it very hard to migrate from other RDBMSs or to import > >data dumped from other databases. > > > >For example, an autoincrement column in MySQL should be an identity column. > >The problem is that when the data is dumped from MySQL to a file, it > >generates inserts with values. These values cant be inserted in the Derby > >table. > > > >Posible solutions: 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. > > > > > > > > > > > >
+1 from me too for "I would be willing to offer as much support as I can, answer questions that are posted, vote on proposals, review submissions, etc."
