To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51517
------- Additional comments from [EMAIL PROTECTED] Wed Jul 6 11:24:24 -0700 2005 ------- Hi, I don't think that HSQLDB has to change. As I said, there's no reason to use identity columns except as the primary key (well, maybe there are reasons, but they are very obscure). Instead, I think the UI should change. If an identity column has been defined, then it should automatically be marked as a primary key. That way, the prompt goes away since the table already has a PK. Furthermore, removing the PK status of an identity column should be impossible. These should be pretty small changes (though I admit I'm not familiar with the code base). The only other problem I can see is if someone tries to set an identity column when there is already a PK. This should probably just give an error to the user (something like, "Cannot create an identity column because the table already has a primary key."). --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
