Mike,
At this point, it is only identified that upgrade needs to do some work to fix duplicate conglomerateids but no details have been discussed as to how to address it.
Mamta
On 6/30/06, Mike Matrigali <[EMAIL PROTECTED]> wrote:
Mamta A. Satoor (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-655?page=all ]
>
> Mamta A. Satoor resolved DERBY-655:
> -----------------------------------
>
> Fix Version: 10.2.0.0
> Resolution: Fixed
>
> Resolving this issue since the patch ensures the uniqueness of conglomerateid for new conglomerates in SYSCONGLOMERATES table. For existing duplicate conglomeratid, work needs to be done at the database upgrade time. DERBY-1343 is open to track upgrade work. As per my knowledge, nobody is working on DERBY-1343 at this point.
>
I missed the original discussion of this issue, I know there are some
pointers in the bug description. After that discussion was there a
consensus on how to address the upgrade issue?
