Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Why comma is expected for auto_increment?

Post

Why comma is expected for auto_increment?

+0
−2
query = "CREATE TABLE "+TABLE+" ("+COLUMN1+" INTEGER PRIMARY KEY NOT NULL AUTO_INCREMENT, "+COLUMN2+" VARCHAR(255), " +
         COLUMN3+" VARCHAR(255), "+COLUMN4+" TEXT, "+ COLUMN5+" VARCHAR(255), "+COLUMN6+" VARCHAR(255), "+COLUMN7+" TEXT)";

error

')',, ON or comma expected, got 'AUTO_INCREMENT'

I am very new to SQL. Earlier I was using Xampp.

Why comma expected for AUTO_INCREMENT? If I write the command something just like this :

"+COLUMN1+" INTEGER PRIMARY KEY NOT NULL ,AUTO_INCREMENT,

then I don't get the error/warning. But I think if I use comma then SQL may think AUTO_INCREMENT isn't for COLUMN1's. Cause it might be separated by comma.

I was trying to follow this answer:

 "CUST_ID" INT not null primary key
        GENERATED ALWAYS AS IDENTITY
        (START WITH 1, INCREMENT BY 1)

But I got same error on GENERATED at first then AS. My attempt is available in the answer.

I have tried IDENTITY also.

Personid int IDENTITY(1,1) PRIMARY KEY,

same error for IDENTITY

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

3 comment threads

Answer!!! (1 comment)
DBMS? (3 comments)
There's two table-column tag. (1 comment)
Answer!!!
Anonymous‭ wrote about 3 years ago

I don't have much more time to write a complete so just putting some information which was helpful for me...

I wasn't using Oracle or T-SQL. I was just using a default SQL in Android Studio.

package android.database.sqlite;

Simply I just can call it SQLITE. And there's no variable called AUTOINCREMENT, AUTOINCREMENT, IDENTITY or GENERATED. And auto-increment related variable isn't required right there. It's not far different from it. So python and android studio is using same SQLITE. I think the same context is available in the documentation (given by Peter)