Issue 52703 - table design: Find a better (more usable) UI for specifiying the initial/increment value of an auto-increment field
Summary: table design: Find a better (more usable) UI for specifiying the initial/incr...
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m120
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: usability
Depends on:
Reported: 2005-08-01 08:13 UTC by Frank Schönheit
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2005-08-01 08:13:47 UTC
When you open the table design for a embedded HSQLDB database, and have a
"Integer" column with "Auto increment" = "Yes", then there is a field
"Auto-increment statement", which is prefilled with "IDENTITY".

Technically, this is fine and correct.

From a user experience point of view, this is
- disturbing: unexperienced users don't know what it is, and will be confused by it
- useless: any other value than IDENTITY doesn't work, anyway

I suggest to remove this field in the table design, if and only if the
database/type already prescribes which information would appear there.
Please also update the specifiction at then :)
Comment 1 ocke.janssen 2005-08-01 08:28:33 UTC
That is not correct. Even HSQLDB supports the creation of auto increment fields
which starts at any number and increment bey any value.

columnname Datatype [(columnSize[,precision])] [{DEFAULT <defaultValue> |

Comment 2 ocke.janssen 2007-08-30 10:06:58 UTC
See my previous comment.
Comment 3 Frank Schönheit 2007-08-30 20:40:03 UTC
Re-opening. The original problem - the fact that the current UI is mere
techno-babble for the unexperienced user - remains. If we want to support users
in creating auto-increments with another initial/step value (do we really? This
is way too advanced for most of them), then we should find an UI which deserves
the word "usable".