Issue 41785 - Unable to edit field definitions and types in a hsqldb table
Summary: Unable to edit field definitions and types in a hsqldb table
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m74
Hardware: All All
: P3 Trivial with 6 votes (vote)
Target Milestone: OOo 2.0
Assignee: marc.neumann
QA Contact: issues@dba
Keywords: oooqa, rfe_eval_ok, usability
: 45507 45620 46543 46660 47400 (view as issue list)
Depends on:
Reported: 2005-02-01 11:07 UTC by dmpop
Modified: 2007-05-21 03:12 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description dmpop 2005-02-01 11:07:36 UTC
Fields (names, data types) in HSQL-based tables cannot be modified after the table has been saved. It 
is, however, possible to delete the existing fields. To reproduce the bug:

1. Create a new HSQL database.
2. Create a nre table.
3. Add some fields.
4. Save table and close.
5. Re-open the table in Design View.
6. The existing fields are not modifiable, but can be deleted.

The issue has been confirmed by other users (see
Comment 1 alex.thurgood 2005-02-07 10:01:23 UTC
confirming on Linux also, setting OS to all, and the oooqa keyword

Comment 2 marc.neumann 2005-02-11 11:38:53 UTC
That would be nice, however I think it's (currently) a limitation of the used
hsqldb database engine. However we should have a look if we can change this.

confirm, set target and reassign to the right developer

Bye Marc
Comment 3 marc.neumann 2005-02-11 11:41:31 UTC
change summary
Comment 4 ocke.janssen 2005-02-11 12:43:23 UTC
At the moment this is not possible. Further information can be found here
, but it is valid RFE so I send it there.
Comment 5 manuj 2005-02-13 20:20:48 UTC
Why not possible ?

Isn't it this command ? :

ALTER TABLE <tablename> ALTER COLUMN <columnname> {RENAME TO <newname> | DROP
DEFAULT | SET DEFAULT <defaultvalue>};

Changes column name. Or adds or drops the default value. 
Comment 6 bettina.haberer 2005-02-17 17:54:37 UTC
Hello Ocke, as it is a defect, it is wrong on the owner 'requirements'. Do you
see a chance to get this fixed for OOo 2.0? 
Comment 7 ocke.janssen 2005-02-18 06:40:17 UTC
Hi Bettina,

I'm sorry, I just forget to set this ot RFE :-)
HSQLDB in it's current state can't simply modify existing column definitions. So
this issue is a RFE.

Best regards,

Comment 8 bettina.haberer 2005-02-18 16:42:41 UTC
Ok, so this one is set to office later.
Comment 9 Frank Schönheit 2005-03-31 12:04:20 UTC
This one is now implemented in CWS hsqldb4. However, it's not yet decided
whether this will be part of 2.0, as the change may have a sever impact on other
functionality, which needs careful testing to prevent regressions. In the
current state towards 2.0, this might be too late ...
Comment 10 Frank Schönheit 2005-03-31 12:05:08 UTC
fixed in CWS hsqldb4
Comment 11 Frank Schönheit 2005-03-31 12:06:13 UTC
*** Issue 45620 has been marked as a duplicate of this issue. ***
Comment 12 Frank Schönheit 2005-04-05 08:03:57 UTC
*** Issue 46543 has been marked as a duplicate of this issue. ***
Comment 13 Frank Schönheit 2005-04-05 08:12:07 UTC
*** Issue 46660 has been marked as a duplicate of this issue. ***
Comment 14 marc.neumann 2005-04-05 09:02:55 UTC
change target to 2.0 (approved by TZ)
Comment 15 Frank Schönheit 2005-04-05 12:24:35 UTC
fs-> msc: please verify in CWS hsqldb4

re-open issue and reassign to msc
Comment 16 Frank Schönheit 2005-04-05 12:24:41 UTC
reassign to msc
Comment 17 Frank Schönheit 2005-04-05 12:24:52 UTC
reset resolution to FIXED
Comment 18 marc.neumann 2005-04-06 10:00:54 UTC
verified in cws hsqldb4
Comment 19 Frank Schönheit 2005-04-06 14:21:02 UTC
*** Issue 45507 has been marked as a duplicate of this issue. ***
Comment 20 marc.neumann 2005-04-18 08:40:11 UTC

fixed in current developer build (version 1.9.m94)-> close.
The current developer build can be found at
Feel free to reopen if this issue is not fixed in the developer build.

Bye Marc
Comment 21 flibby05 2005-04-21 14:43:25 UTC
*** Issue 47400 has been marked as a duplicate of this issue. ***
Comment 22 davesmith 2005-12-31 18:57:07 UTC
Although this problem is marked as resolved, it has reproduced itself for me. I
am using OOo 2.0.1, KDE and FC4. I have exactly this problem, although when I
use OOo on a machine using Win2000 I cannot reproduce the problem.
Comment 23 jeffos2 2007-05-21 03:12:34 UTC
I've been searching around and I think this is the right
issue, but if not, please point me to the right place.

Though this issue is marked as CLOSED and FIXED it doesn't
seem to be.

First, the particulars:

Platform:       WinXP Pro SP2+
ProductVersion: 2.2
SolarVersion:   680
DBMS:           HSQLDB 1.8.07 (In SERVER mode)

If one opens the BASE document and selects an existing table to edit
the ability to edit either the Description or the Format of the column
is disabled. Thus the problem. It should always be possible to edit
both the Column Description and the Format of the Column.

Please note that these are, to my limited knowledge, concepts internal
to the Office. Description seems to map to HelpText and Format to the
NumberFormat Service (or something like that).

Interesting variations on the problem.

If the DataSource is ODBC the behavior is as described above.

If the DataSource is ADO then both Description and Format is editable
plus (in the box to the right) the text is:
    "This is where you determine the output format of the data."
where as, in the previous two cases, the box is blank.

Please advise.