Update README

Author: owjs3901

CLAUDE.md

@@ -46,7 +46,7 @@ cargo run -p vespertide-cli -- log
 2. **Baseline Reconstruction**: Applied migrations are replayed to rebuild the baseline schema
 3. **Diffing**: Current models are compared against the baseline to compute changes
 4. **Planning**: Changes are converted into a `MigrationPlan` with versioned actions
-5. **SQL Generation**: Migration actions are translated into PostgreSQL SQL statements
+5. **SQL Generation**: Migration actions are translated into SQL statements
 
 ### Crate Responsibilities
 
@@ -59,7 +59,7 @@ cargo run -p vespertide-cli -- log
   - `plan_next_migration()`: Combines baseline reconstruction + diffing to create the next migration
   - `apply_action()`: Applies a single migration action to a schema (used during replay)
   - `validate_*()`: Validates schemas and migration plans
-- **vespertide-query**: Converts `MigrationAction` → PostgreSQL SQL with bind parameters
+- **vespertide-query**: Converts `MigrationAction` → SQL with bind parameters
   - Uses `ColumnType::to_sql()` method for SQL type conversion
 - **vespertide-config**: Manages `vespertide.json` (models/migrations directories, naming case preferences)
 - **vespertide-cli**: Command-line interface implementation
@@ -111,7 +111,7 @@ SimpleColumnType::Integer.into()
 
 ### ColumnType Methods
 `ColumnType` provides two utility methods:
-- `to_sql()`: Returns the PostgreSQL SQL type string (e.g., `"INTEGER"`, `"VARCHAR(255)"`)
+- `to_sql()`: Returns the SQL type string (e.g., `"INTEGER"`, `"VARCHAR(255)"`)
 - `to_rust_type(nullable: bool)`: Returns the Rust type string for SeaORM entity generation (e.g., `"i32"` or `"Option<i32>"`)
 
 These methods replace the old standalone functions `column_type_sql()` and `rust_type()`.
@@ -134,7 +134,7 @@ pub struct ForeignKeyDef {
 - The planner validates that column/table names follow the configured naming case
 
 ### SQL Generation Target
-All SQL generation currently targets **PostgreSQL only**. When modifying the query builder, ensure PostgreSQL compatibility.
+SQL generation currently uses PostgreSQL-compatible syntax. The query builder can be extended to support other database systems.
 
 ### JSON Schema Generation
 The `vespertide-schema-gen` crate uses `schemars` to generate JSON Schemas from the Rust types. After modifying core data structures, regenerate schemas with:
@@ -155,4 +155,4 @@ Schema base URL can be overridden via `VESP_SCHEMA_BASE_URL` environment variabl
 
 - YAML loading is not implemented (templates can be generated but not parsed)
 - Runtime migration executor (`run_migrations`) in `vespertide-macro` is not implemented
-- Only PostgreSQL SQL generation is supported
+- SQL generation currently uses PostgreSQL-compatible syntax

Cargo.lock

@@ -1,6 +1,6 @@
 # Vespertide
 
-Declarative database schema management for PostgreSQL. Define your schemas in JSON, and Vespertide automatically generates migration plans and SQL from model diffs.
+Declarative database schema management. Define your schemas in JSON, and Vespertide automatically generates migration plans and SQL from model diffs.
 
 [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
 [![GitHub Actions](https://img.shields.io/github/actions/workflow/status/dev-five-git/vespertide/CI.yml?branch=main&label=CI)](https://github.com/dev-five-git/vespertide/actions)
@@ -12,7 +12,7 @@ Declarative database schema management for PostgreSQL. Define your schemas in JS
 - **Declarative Schema**: Define your desired database state in JSON files
 - **Automatic Diffing**: Vespertide compares your models against applied migrations to compute changes
 - **Migration Planning**: Generates typed migration actions (not raw SQL) for safety and portability
-- **PostgreSQL SQL Generation**: Converts migration actions to parameterized PostgreSQL statements
+- **SQL Generation**: Converts migration actions to parameterized SQL statements
 - **JSON Schema Validation**: Ships with JSON Schemas for IDE autocompletion and validation
 - **ORM Export**: Export schemas to SeaORM entities
 
@@ -76,7 +76,7 @@ Models are JSON files in the `models/` directory:
 ### Column Types
 
 **Simple Types** (string values in JSON):
-| Type | PostgreSQL |
+| Type | SQL Type |
 |------|------------|
 | `"integer"` | INTEGER |
 | `"big_int"` | BIGINT |
@@ -128,7 +128,7 @@ See [SKILL.md](SKILL.md) for complete documentation on model definitions.
 vespertide/
 ├── vespertide-core      # Data structures (TableDef, ColumnDef, MigrationAction)
 ├── vespertide-planner   # Schema diffing and migration planning
-├── vespertide-query     # PostgreSQL SQL generation
+├── vespertide-query     # SQL generation
 ├── vespertide-config    # Configuration management
 ├── vespertide-cli       # Command-line interface
 ├── vespertide-exporter  # ORM code generation (SeaORM)
@@ -142,7 +142,7 @@ vespertide/
 2. **Replay Migrations**: Applied migrations are replayed to reconstruct the baseline schema
 3. **Diff Schemas**: Current models are compared against the baseline
 4. **Generate Plan**: Changes are converted into typed `MigrationAction` enums
-5. **Emit SQL**: Migration actions are translated to PostgreSQL SQL
+5. **Emit SQL**: Migration actions are translated to SQL
 
 ## Configuration
 
@@ -179,7 +179,7 @@ cargo run -p vespertide-schema-gen -- --out schemas
 
 ## Limitations
 
-- SQL generation targets **PostgreSQL only**
+- SQL generation currently uses PostgreSQL-compatible syntax
 - YAML loading is not yet implemented (templates can be generated but not parsed)
 - Runtime migration executor is not implemented
 

README.md

@@ -1,11 +1,11 @@
 ---
 name: vespertide
-description: Define PostgreSQL database schemas in JSON and generate migration plans. Use this skill when creating or modifying database models, defining tables with columns, constraints, indexes, and foreign keys for Vespertide-based projects.
+description: Define database schemas in JSON and generate migration plans. Use this skill when creating or modifying database models, defining tables with columns, constraints, indexes, and foreign keys for Vespertide-based projects.
 ---
 
 # Vespertide Database Schema Definition
 
-This skill helps you create and manage database models using Vespertide, a declarative schema management tool for PostgreSQL.
+This skill helps you create and manage database models using Vespertide, a declarative schema management tool.
 
 ## Installation
 
@@ -79,7 +79,7 @@ Column types in JSON can be either simple (string) or complex (object) values.
 
 Simple types are represented as strings in JSON (snake_case):
 
-| Type | PostgreSQL | Use Cases |
+| Type | SQL Type | Use Cases |
 |------|------------|-----------|
 | `"small_int"` | SMALLINT | Small integers (-32768 to 32767) |
 | `"integer"` | INTEGER | IDs, counters |

SKILL.md

@@ -28,7 +28,7 @@ pub enum ColumnType {
 }
 
 impl ColumnType {
-    /// Convert column type to PostgreSQL SQL type string
+    /// Convert column type to SQL type string
     pub fn to_sql(&self) -> String {
         match self {
             ColumnType::Simple(ty) => match ty {

crates/vespertide-core/src/schema/column.rs

@@ -6,7 +6,7 @@ license.workspace = true
 repository.workspace = true
 homepage.workspace = true
 documentation.workspace = true
-description = "Converts migration actions into PostgreSQL SQL statements with bind parameters"
+description = "Converts migration actions into SQL statements with bind parameters"
 
 [dependencies]
 vespertide-core = { workspace = true }

crates/vespertide-query/Cargo.toml

@@ -202,7 +202,7 @@ pub fn build_action_queries(action: &MigrationAction) -> Result<Vec<BuiltQuery>,
             // For removing constraints, we need to handle each type differently
             let drop_sql = match constraint {
                 TableConstraint::PrimaryKey { .. } => {
-                    // PostgreSQL syntax for dropping primary key
+                    // Syntax for dropping primary key
                     format!("ALTER TABLE {t} DROP CONSTRAINT {t}_pkey;")
                 }
                 TableConstraint::Unique { name, columns } => {