You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-user@db.apache.org by Georgi Naplatanov <go...@oles.biz> on 2006/01/13 15:15:14 UTC
too many waiting objects
Hello, ddlutils is a great tool,
i try to migrate hsqldb database to apache derby and i have
synchronization problem with autogenerated keys from the old (source) db
and new values from the new db (target db - derby).
Lets say we hawe one row from the parent table
parent table - old db
pk autoincrement - id = 35
parent table- new db
pk autoincrement - id = 2
In this case ddlutils can't insert rows to the tables wich has fk from
parent tables because id value was changed from 35 to 2.
For apache derby i use attached pach for lastInsertedId implementation
Regards
Re: too many waiting objects
Posted by Georgi Naplatanov <go...@oles.biz>.
Thomas Dudziak wrote:
>On 1/13/06, Georgi Naplatanov <go...@oles.biz> wrote:
>
>
>
>>Hello, ddlutils is a great tool,
>>i try to migrate hsqldb database to apache derby and i have
>>synchronization problem with autogenerated keys from the old (source) db
>>and new values from the new db (target db - derby).
>>
>>Lets say we hawe one row from the parent table
>>
>>parent table - old db
>>pk autoincrement - id = 35
>>
>>
>>parent table- new db
>>pk autoincrement - id = 2
>>
>>In this case ddlutils can't insert rows to the tables wich has fk from
>>parent tables because id value was changed from 35 to 2.
>>
>>For apache derby i use attached pach for lastInsertedId implementation
>>
>>
>
>Could you add this as a bug to DdlUtils' JIRA ?
>
>Tom
>
>
Done
https://issues.apache.org/jira/browse/DDLUTILS-64
Re: too many waiting objects
Posted by Thomas Dudziak <to...@gmail.com>.
On 1/13/06, Georgi Naplatanov <go...@oles.biz> wrote:
> Hello, ddlutils is a great tool,
> i try to migrate hsqldb database to apache derby and i have
> synchronization problem with autogenerated keys from the old (source) db
> and new values from the new db (target db - derby).
>
> Lets say we hawe one row from the parent table
>
> parent table - old db
> pk autoincrement - id = 35
>
>
> parent table- new db
> pk autoincrement - id = 2
>
> In this case ddlutils can't insert rows to the tables wich has fk from
> parent tables because id value was changed from 35 to 2.
>
> For apache derby i use attached pach for lastInsertedId implementation
Could you add this as a bug to DdlUtils' JIRA ?
Tom