insertr

joakim/insertr

Fork 0

Commit Graph

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

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

2 Commits