Issue 48477 - Base create table wizard incorrectly uses AUTO_INCREMENT instead of IDENTITY to create an autovalue integer.
Summary: Base create table wizard incorrectly uses AUTO_INCREMENT instead of IDENTITY ...
Status: CLOSED DUPLICATE of issue 48480
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m95
Hardware: PC Windows 2000
: P3 Trivial with 2 votes (vote)
Target Milestone: OOo 2.0.1
Assignee: berend.cornelius
QA Contact: issues@dba
URL:
Keywords:
: 48766 49687 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-04-29 18:39 UTC by lleland
Modified: 2006-05-31 14:29 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 lleland 2005-04-29 18:39:30 UTC
Using the table wizard in Base on an HSQL database, when you ask it to
automatically create a primary key auto value field, you get the following error
message:
  Unexpected token: AUTO_INCREMENT in statement [CREATE TABLE "Contacts" ("ID"
INTEGER NOT NULL auto_increment]

Base is trying to use the "auto_increment" keyword to designate an autovalue
field. In HSQL the proper keyword is "IDENTITY".
Comment 1 christoph.lukasiak 2005-05-02 13:52:26 UTC
clu->oj: i can repro that
Comment 2 christoph.lukasiak 2005-05-02 13:53:35 UTC
set target
Comment 3 lleland 2005-05-03 02:05:40 UTC
2.0.1??? If this bug is not fixed for the initial 2.0 release, you cannot create
a table with an autovalue using the Base table wizard at all. You cannot even
edit it after creation (see issue #48480). You are forced to only use the design
view making the wizard useless. This is a *very* serious flaw which will lose
you all users who are not proficient enough to feel comfortable using design
view. This is definitely serious enough to override any code or issue priorty
freeze.
Comment 4 ocke.janssen 2005-05-03 06:43:13 UTC
The table wizard belongs to you.
Comment 5 Frank Schönheit 2005-05-23 07:17:42 UTC
*** Issue 48766 has been marked as a duplicate of this issue. ***
Comment 6 Frank Schönheit 2005-05-23 07:18:08 UTC
*** Issue 49687 has been marked as a duplicate of this issue. ***
Comment 7 berend.cornelius 2005-05-27 14:07:44 UTC
BC: According to OJ fixed for PP1-> duplicate to bug i48480

*** This issue has been marked as a duplicate of 48480 ***
Comment 8 berend.cornelius 2006-04-07 11:34:08 UTC
bc: verified again in the master of SRC680 m162. Closing issue