🐛 Fix migration for SQLite compatibility in CI/CD

The migration was failing in CI/CD because SQLite doesn't support:
- ALTER COLUMN ... DROP NOT NULL syntax
- ON CONFLICT (postgres) vs INSERT OR IGNORE (sqlite)

Fixed by:
- Checking dialect.name and skipping ALTER COLUMN for SQLite
- Using INSERT OR IGNORE for SQLite, ON CONFLICT for PostgreSQL
- Using 1 instead of true for SQLite boolean values

This allows the migration to work in both production (PostgreSQL)
and testing (SQLite) environments.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: claude

migrations/versions/c8c8f157177a_enhanced_property_model_with_.py

@@ -151,21 +151,36 @@ def upgrade():
     # Phase 5: Migrate existing contact_id relationships to PropertyContact table
     # This preserves existing relationships during the transition
     connection = op.get_bind()
-    result = connection.execute(sa.text("""
-        INSERT INTO property_contact (property_id, contact_id, relationship_type, is_primary, created_at)
-        SELECT id, contact_id, 'owner', true, CURRENT_TIMESTAMP
-        FROM property
-        WHERE contact_id IS NOT NULL
-        ON CONFLICT (property_id, contact_id) DO NOTHING
-    """))
+    from alembic import context
+    
+    # SQLite uses different syntax for INSERT ... ON CONFLICT
+    if context.get_context().dialect.name == 'sqlite':
+        result = connection.execute(sa.text("""
+            INSERT OR IGNORE INTO property_contact (property_id, contact_id, relationship_type, is_primary, created_at)
+            SELECT id, contact_id, 'owner', 1, CURRENT_TIMESTAMP
+            FROM property
+            WHERE contact_id IS NOT NULL
+        """))
+    else:
+        # PostgreSQL syntax
+        result = connection.execute(sa.text("""
+            INSERT INTO property_contact (property_id, contact_id, relationship_type, is_primary, created_at)
+            SELECT id, contact_id, 'owner', true, CURRENT_TIMESTAMP
+            FROM property
+            WHERE contact_id IS NOT NULL
+            ON CONFLICT (property_id, contact_id) DO NOTHING
+        """))
 
     # Log migration progress
     if result.rowcount > 0:
         print(f"Migrated {result.rowcount} existing property-contact relationships")
 
     # Phase 6: Make contact_id nullable for backward compatibility
     # This allows properties to be created without requiring a contact_id
-    op.alter_column('property', 'contact_id', nullable=True)
+    # Note: SQLite doesn't support ALTER COLUMN, so we need to check the database type
+    from alembic import context
+    if context.get_context().dialect.name != 'sqlite':
+        op.alter_column('property', 'contact_id', nullable=True)
 
     # Note: We're keeping the contact_id column for now to ensure backward compatibility
     # It can be removed in a future migration after all code is updated