Fix auto increament on sqlite

.changepacks/changepack_log_KYO7bQOcPhhU8kIwATtUP.json

@@ -0,0 +1 @@
+{"changes":{"crates/vespertide-config/Cargo.toml":"Patch","crates/vespertide-exporter/Cargo.toml":"Patch","crates/vespertide-naming/Cargo.toml":"Patch","crates/vespertide-loader/Cargo.toml":"Patch","crates/vespertide/Cargo.toml":"Patch","crates/vespertide-query/Cargo.toml":"Patch","crates/vespertide-cli/Cargo.toml":"Patch","crates/vespertide-macro/Cargo.toml":"Patch","crates/vespertide-planner/Cargo.toml":"Patch","crates/vespertide-core/Cargo.toml":"Patch"},"note":"Fix auto increament issue on sqlite","date":"2026-01-15T12:38:07.170780700Z"}

SKILL.md

@@ -56,6 +56,28 @@ cargo install vespertide-cli
 
 ---
 
+## Exported ORM Files (DO NOT EDIT)
+
+> **CRITICAL**: Files generated by `vespertide export` are AUTO-GENERATED. Never modify them manually.
+
+### Rules
+
+1. **Never manually edit** exported files (SeaORM entities, SQLAlchemy models, etc.)
+2. **Always regenerate** by running `vespertide export --orm <orm_name>`
+3. **Edit source models** in `models/*.json` instead, then re-export
+
+### Workflow
+
+```bash
+# 1. Edit your model files (models/*.json)
+# 2. Regenerate ORM code
+vespertide export --orm seaorm
+
+# 3. Never touch the generated files after this
+```
+
+---
+
 ## Migration Files (DO NOT EDIT)
 
 > **CRITICAL**: Migration files are AUTO-GENERATED. Never create or modify them manually.
@@ -625,6 +647,7 @@ Both columns with `"primary_key": true` creates a **single composite primary key
 3. **Never add NOT NULL columns without default** - Requires `fill_with` in migration
 4. **Never use table-level constraints** - Except for CHECK expressions only
 5. **Never manually create/edit migration files** - Only `fill_with` exception
+6. **Never manually edit exported ORM files** - Use `vespertide export` to regenerate
 
 ### Naming Conventions
 

crates/vespertide-query/src/sql/create_table.rs

@@ -49,6 +49,11 @@ pub(crate) fn build_create_table_for_backend(
 
         // Apply auto_increment if this column is in the auto_increment primary key
         if auto_increment_columns.contains(column.name.as_str()) {
+            // For SQLite, AUTOINCREMENT requires inline PRIMARY KEY (INTEGER PRIMARY KEY AUTOINCREMENT)
+            // So we must call primary_key() on the column even if there's a table-level PRIMARY KEY
+            if matches!(backend, DatabaseBackend::Sqlite) {
+                col.primary_key();
+            }
             col.auto_increment();
         }
 
@@ -64,8 +69,13 @@ pub(crate) fn build_create_table_for_backend(
         match constraint {
             TableConstraint::PrimaryKey {
                 columns: pk_cols,
-                auto_increment: _,
+                auto_increment,
             } => {
+                // For SQLite with auto_increment, skip table-level PRIMARY KEY
+                // because AUTOINCREMENT requires inline PRIMARY KEY on the column
+                if matches!(backend, DatabaseBackend::Sqlite) && *auto_increment {
+                    continue;
+                }
                 // Build primary key index
                 let mut pk_idx = Index::create();
                 for c in pk_cols {

crates/vespertide-query/src/sql/snapshots/vespertide_query__sql__create_table__tests__create_table_with_auto_increment_primary_key@create_table_with_auto_increment_Sqlite.snap

@@ -2,4 +2,4 @@
 source: crates/vespertide-query/src/sql/create_table.rs
 expression: sql
 ---
-CREATE TABLE "users" ( "id" integer NOT NULL AUTOINCREMENT, PRIMARY KEY ("id") )
+CREATE TABLE "users" ( "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT )

crates/vespertide-query/src/sql/snapshots/vespertide_query__sql__create_table__tests__create_table_with_inline_auto_increment_primary_key@create_table_with_inline_auto_increment_Sqlite.snap

@@ -2,4 +2,4 @@
 source: crates/vespertide-query/src/sql/create_table.rs
 expression: sql
 ---
-CREATE TABLE "users" ( "id" integer NOT NULL AUTOINCREMENT, PRIMARY KEY ("id") )
+CREATE TABLE "users" ( "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT )