Bug 33736 - No Auto-increment checkbox (or such) in table design
Summary: No Auto-increment checkbox (or such) in table design
Status: CLOSED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.3.0 RC4
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-30 15:04 UTC by Patrik Arvhult
Modified: 2011-02-03 06:09 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrik Arvhult 2011-01-30 15:04:29 UTC
When creating a table with the guide theres a way to get auto-inkrement
of the primary key.

If I instead create a table with the table design, there is the option
to specify what field to use for primary key, but theres no checkbox
or such option to give it the auto-increment attribute.

Using the table design for quickly makeing exactly the table you need, it later wont work with forms...

I think this is important to fix because this bug makes openoffice base messy to work with.
Comment 1 Patrik Arvhult 2011-01-30 15:06:04 UTC
(In reply to comment #0)
> When creating a table with the guide theres a way to get auto-inkrement
> of the primary key.
> 
> If I instead create a table with the table design, there is the option
> to specify what field to use for primary key, but theres no checkbox
> or such option to give it the auto-increment attribute.
> 
> Using the table design for quickly makeing exactly the table you need, it later
> wont work with forms...
> 
> I think this is important to fix because this bug makes openoffice base messy
> to work with.

*Libreoffice* ;)
Comment 2 Drew Jensen 2011-01-30 15:26:43 UTC
Actually there is a way to designate PK in table design view. (albeit rather hidden) It is a right click menu choice. If you click on the left edge of the row you want to designate. ( for multi-field PK select multiple rows first)

You can also set auto_increment for integer fields (auto value setting in the GUI)

 - but this isn't the right spot for support questions. This is covered in the help file and of course please make use of either the user mailing list or the web forum.

(one shortcut not in the help file, BTW, for a hsql database the first integer field set to Auto_Increment [auto value] will automatically be designated as the PK if not explicitly defined. )
Comment 3 Patrik Arvhult 2011-01-30 16:03:56 UTC
Theres no hint
 (In reply to comment #2)
> Actually there is a way to designate PK in table design view. (albeit rather
> hidden) It is a right click menu choice. If you click on the left edge of the
> row you want to designate. ( for multi-field PK select multiple rows first)
> 
> You can also set auto_increment for integer fields (auto value setting in the
> GUI)
> 
>  - but this isn't the right spot for support questions. This is covered in the
> help file and of course please make use of either the user mailing list or the
> web forum.
> 
> (one shortcut not in the help file, BTW, for a hsql database the first integer
> field set to Auto_Increment [auto value] will automatically be designated as
> the PK if not explicitly defined. )

Yes i easily/naturally found the popup to specify the field to be primary key
but I guess new users might fall in this trap if they define the field as
numeric instead of integer. There could easily be gudance by more options in the popup:

"Primary key"
"Integer & auto-inc primary key" or "Change to integer & auto-inc primary key"

Then less people will have trouble.

/ Patrik


   

 theres no hint to use an integer field instead of a numeric field
to get the auto-increment option. Maybe this went a support issue on the other hand it can be seen as a usability issue - if theres a trap - tell about it.
Comment 4 Drew Jensen 2011-01-30 16:38:54 UTC
*chuckle* - tribal knowledge

There are plenty of UX issues to be found in Base - not sure how the developers here would want to handle things like this, if they would want you or someone, to alter this issue so that is a RFE based on the usability issue or not. I do not believe it is intended to use the issue tracker that way, but I don't really know.
Comment 5 Alex Thurgood 2011-02-03 06:09:11 UTC
IMHO this is not a bug, the functionality is already there as has been explained. If anything, you should file a RFE (request for enhancement). Closing.


Alex