Issue 67295 - Activate AutoValue by default when adding Primary Key
Summary: Activate AutoValue by default when adding Primary Key
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.3
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-12 22:31 UTC by Andrea Pescetti
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Andrea Pescetti 2006-07-12 22:31:59 UTC 
1. Create a new database.
2. Create a table in Design View, add a couple of VARCHAR fields.
3. Save the table; OOo warns that it is advised to create a Primary Key.
4. Accept.

The Primary Key field thus created has AutoValue set to off. It would be far
easier for users if it was set to on, as this is the expected behaviour for an
ID field.

[Reported by Mario Govoni during Italian QA tests]
Comment 1 christoph.lukasiak 2006-07-17 10:22:27 UTC 
in this case there also must be a pre check if the database support such things
... send further to the requirements team