To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103682 Issue #|103682 Summary|HSQLDB Index lost (Violation of unique constraint SYS_ |PK_260...) Component|Database access Version|OOo 3.1 Platform|PC URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|none Assigned to|dbaneedsconfirm Reported by|windl
------- Additional comments from [email protected] Tue Jul 21 07:50:33 +0000 2009 ------- In a database design with many tables and relations, one table has an INTEGER ID that is used as primary key, and it's value is autoincremented. After some time I could not enter any new data into that table. The error message was: Violation of unique constraint SYS_PK_260: duplicate value(s) for column(s) "ID" in statement [INSERT INTO "LSystem_VDisk" ("LSystem_ID", "valid_from", "VDisk_ID") VALUES(?,?,?)] As closing/re-opening the table did not work, just as closing/re-opening the application did not, I tried something like "rebuilding the index" (which does not exist). As the index is not used in a releation, I though I could drop it and then re-create it. When I tried to drop the index (or modify it), I get another error: Index not found: SYS_IDX_259 in statement [DROP INDEX "SYS_IDX_259" ON "LSystem_VDisk"] This could be yet another bug in HSQLDB, but maybe the view of StarOffice isn't in sync with HSQLDB. Actual Product is StarOffice 9 Update 2 --------------------------------------------------------------------- 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]
