Skip to content

✅ Critical Bug Fix Released: v0.1.3
Compare
Choose a tag to compare
@greysquirr3l greysquirr3l released this 23 Jun 03:25
· 51 commits to main since this release
v0.1.3
This tag was signed with the committer’s verified signature.
greysquirr3l Nick Campbell
GPG key ID: 902DADBBDD5E203D
Verified
Learn about vigilant mode.
3095413
This commit was signed with the committer’s verified signature.
greysquirr3l Nick Campbell
GPG key ID: 902DADBBDD5E203D
Verified
Learn about vigilant mode.

✅ Critical Bug Fix Released: v0.1.3
🚨 Issue Resolved
The external project was experiencing nil pointer panics when calling:

🔧 Root Cause Found
GORM expected the interface method to be named GetDBConn(), but we had implemented GetDBConnector(). This mismatch caused GORM's db.DB() method to return nil.

✅ Fix Applied
Corrected interface method: GetDBConnector() → GetDBConn()
Added comprehensive test: TestDBMethod() validates db.DB() functionality
Verified compatibility: All database access patterns now work correctly
📊 Validation
✅ All existing tests pass
✅ New test specifically validates db.DB() returns valid *sql.DB
✅ Connection pool management works correctly
✅ Database cleanup operations function properly
🚀 Release Information
Repository: https://github.com/greysquirr3l/gorm-duckdb-driver
Latest Version: v0.1.3
Installation: go get github.com/greysquirr3l/gorm-duckdb-driver@v0.1.3
⚡ Recommendation
All users should upgrade to v0.1.3 immediately to avoid nil pointer issues with database cleanup operations.

This critical fix ensures the driver is fully compatible with GORM's standard database access patterns and resolves integration failures reported by external projects.

Assets 2
Loading