To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104901
User fs changed the following:
What |Old value |New value
================================================================================
Assigned to|dbaneedsconfirm |oj
--------------------------------------------------------------------------------
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
--------------------------------------------------------------------------------
Priority|P3 |P2
--------------------------------------------------------------------------------
Target milestone|--- |OOo 3.2
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Wed Sep 9 07:54:25 +0000
2009 -------
confirming, assigning, promoting to P2 - it effectively corrupts the DB -,
targeting to OOo 3.2.
@ud: Thanks for this excellent bug description
@oj: This sounds like a combination of an OOo and HSQL bug to me. First,
changing the column default should not touch the HSQL table at all - the default
value is a mere client-side property, isn't it? That's the OOo part. Second,
even if we tell HSQL to change a column definition, it shouldn't implicitly
reset the auto-increment value sequence. Please investigate whether you find the
reason/fix for this in the HSQL sources.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
