Issue 54583 - TableWizard: Problems occur with AutoValue fields
Summary: TableWizard: Problems occur with AutoValue fields
Status: ACCEPTED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-14 09:52 UTC by berend.cornelius
Modified: 2017-05-20 10:48 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description berend.cornelius 2005-09-14 09:52:53 UTC
If you assign the attribute "AutoValue" to a numerical field of the second page
of the tablewizard, this is automatically used as the primary key field of the
table. In fact at least in a hsql database the third page of the wizard, where
the primary key fields are assigned (in other databases this might even work)
should be disabled. One implementation problem I currently see is that the
control group on the second page where the field attributes are set must offer a
listener to notify the wizard when such changes have been assigned by the user
so that the wizard can immediately disable the according step. Another problem I
found in this respect is that the automatically added primary key field "ID"
must be shown among the other fields on the first and second step, because after
the failure of the creation of a table for whatever the reason is there is no
possibility to remove this field.
Comment 1 berend.cornelius 2005-12-16 15:41:54 UTC
BC: Reduce target to OOo 2.0.3
Comment 2 berend.cornelius 2006-02-03 15:39:36 UTC
bc: As discussed the problem with fs I send the bug to him. As he could attest
it is a special problem with HSQL database  where autovalue fields are
automatically taken over as primary key fields. As database dependent logics
should not be used in any of the wizards I send the bug to the Base team first,
so they can find an appropriate solution.

I extracted the bug about the "ID" field mentioned above into issue 61582.
Comment 3 berend.cornelius 2006-02-03 15:41:41 UTC
bc->fs: As discussed with KSO we wouldn't object to reducing the target from PP3
 to 'Office later'
Comment 4 Frank Schönheit 2006-03-13 12:36:55 UTC
don't consider this 2.0.3-relevant ....
Comment 5 Marcus 2017-05-20 10:48:12 UTC
Reset assigne to the default "issues@openoffice.apache.org".