Apache OpenOffice (AOO) Bugzilla – Issue 45507
Can not modify table structure of HSQL tables
Last modified: 2013-08-07 15:45:41 UTC
I have an existing external HSQL database. I have established a connection to it via OOo 2.0 beta and opened up a table for editing. I can enter data into the table's fields but I cannot edit any of the fields' properties because they are "greyed out" and disabled. Please see screen grab for a visual demonstration.
Created attachment 24046 [details] Image of editing a table where field properties are uneditable
I could be mistaken, but I thought that as of the 2.0 Beta, you could not edit the properties for existing columns. I think that this feature was not even added to HSQLDB until recently.... I have verfied that this is the case for the 2.0 Beta, but the fix may already exist in a later build. I think that I noticed somewhere that the functionality was finally complete. I do not see this listed here, however: http://hsqldb.sourceforge.net/web/openoffice.html
*** Issue 45467 has been marked as a duplicate of this issue. ***
Right, HSQLDB cannot yet (except in the latest release candidate for 1.8.0) change the definition of existing fields. Also, OOo is not yet prepared to use this feature in HSQLDB.
From what I gather from the comments, this issue should be resolved invalid because OOo does not support the feature that the reporter says is not working. If this is correct, or if no other relvant information becomes available by April 5, I vote that this issue be Resolved Invalid.
Rather than marking it invalid (it IS a VALID issue as, for me, it makes Base more or less useless as a database) I suggest that it remain open but the type changed to a feature request (if possible to change issue type) to be implemented when or not long after HSQLDB supports this feature (currently working in the next beta). Unless, of course, this is already slated for a future release of OOo, which I strongly suspect it is. Then the issue should be resolved in the appropriate manner. Whatever the outcome this is NOT an invalid issue IMHO and I think people should be able to still vote on how much they want this feature implemented. Thanks.
mark_jones, I agree. Resolving invalid does not mean that it is forever closed and never to be dealt with again. It simply means "The problem described is not an issue." If, as the comments indicate, this is a feature that OOo does not yet have, but maybe will one day, changing it to an enhancement request would be the best course. As of now, it is technically invalid because it does not describe a problem in the current version of the software. http://www.openoffice.org/scdocs/issue_lifecycle.html
change target, change prio, change to enhancement and reassign to default owner
meanwhile fixes as issue 41785 :) *** This issue has been marked as a duplicate of 41785 ***
closing duplicate