3 Commits

Author	SHA1	Message	Date
Joakim	4dc479ba9e	docs: clarify sqlc DDL support limitations and correct implementation ... **Discovery**: sqlc's DDL support is database-engine specific: ✅ **PostgreSQL**: sqlc generates functions for CREATE INDEX, CREATE FUNCTION ❌ **SQLite**: sqlc does NOT generate CREATE INDEX functions ❌ **Both**: sqlc does NOT generate CREATE TRIGGER functions **Corrected Implementation**: - Use sqlc-generated setup functions where available (tables always, PostgreSQL indexes) - Use manual SQL where sqlc doesn't support (SQLite indexes, all triggers) - Comments clarify why manual SQL is needed in each case **Architecture Principle**: Use sqlc for what it supports, supplement with manual SQL for what it doesn't - this is the recommended hybrid approach.	2025-09-09 00:28:10 +02:00
Joakim	bab329b429	refactor: implement database-specific schema architecture with schema-as-query pattern ... 🏗️ **Major Database Schema Refactoring** **Problem Solved**: Eliminated model duplication and multiple sources of truth by: - Removed duplicate models (`internal/models/content.go`) - Replaced inlined schema strings with sqlc-generated setup functions - Implemented database-specific schemas with proper NOT NULL constraints **Key Improvements**: ✅ **Single Source of Truth**: Database schemas define all types, no manual sync needed ✅ **Clean Generated Types**: sqlc generates `string` and `int64` instead of `sql.NullString/sql.NullTime` ✅ **Schema-as-Query Pattern**: Setup functions generated by sqlc for type safety ✅ **Database-Specific Optimization**: SQLite INTEGER timestamps, PostgreSQL BIGINT timestamps ✅ **Cross-Database Compatibility**: Single codebase supports both SQLite and PostgreSQL **Architecture Changes**: - `db/sqlite/` - SQLite-specific schema and setup queries - `db/postgresql/` - PostgreSQL-specific schema and setup queries - `db/queries/` - Cross-database CRUD queries using `sqlc.arg()` syntax - `internal/db/database.go` - Database abstraction with runtime selection - `internal/api/models.go` - Clean API models for requests/responses **Version Control System**: Complete element-level history with user attribution and rollback **Verification**: ✅ Full API workflow tested (create → update → rollback → versions) **Production Ready**: Supports SQLite (development) → PostgreSQL (production) migration	2025-09-09 00:25:07 +02:00
Joakim	161c320304	feat: complete full-stack development integration ... 🎯 Major Achievement: Insertr is now a complete, production-ready CMS ## 🚀 Full-Stack Integration Complete - ✅ HTTP API Server: Complete REST API with SQLite database - ✅ Smart Client Integration: Environment-aware API client - ✅ Unified Development Workflow: Single command full-stack development - ✅ Professional Tooling: Enhanced build, status, and health checking ## 🔧 Development Experience - Primary: `just dev` - Full-stack development (demo + API server) - Alternative: `just demo-only` - Demo site only (special cases) - Build: `just build` - Complete stack (library + CLI + server) - Status: `just status` - Comprehensive project overview ## 📦 What's Included - **insertr-server/**: Complete HTTP API server with SQLite database - **Smart API Client**: Environment detection, helpful error messages - **Enhanced Build Pipeline**: Builds library + CLI + server in one command - **Integrated Tooling**: Status checking, health monitoring, clean workflows ## 🧹 Cleanup - Removed legacy insertr-old code (no longer needed) - Simplified workflow (full-stack by default) - Updated all documentation to reflect complete CMS ## 🎉 Result Insertr is now a complete, professional CMS with: - Real content persistence via database - Professional editing interface - Build-time content injection - Zero-configuration deployment - Production-ready architecture Ready for real-world use! 🚀	2025-09-08 19:40:09 +02:00