🟠 MongoDB not supported end-to-end: DI container is GORM-shaped (NewPostgres…/*gorm.DB)

[sazardev]

Severity: 🟠 HIGH — --database mongodb does not compile end-to-end

After the 1.25.x fixes, a MongoDB project's main.go and repository now compile, but the DI container is generated GORM-shaped and breaks the build.

Reproduction

goca init m --module github.com/test/m --database mongodb
cd m
goca feature Item --fields "name:string,qty:int"
goca integrate --all
go build ./...

Actual

internal/di/container.go: undefined: repository.NewPostgresItemRepository

internal/di/container.go is generated with db *gorm.DB, NewContainer(db *gorm.DB) and repository.NewPostgresItemRepository(c.db), but the MongoDB repository constructor is NewMongoItemRepository(db *mongo.Database), and the Mongo main.go exposes a mongoClient *mongo.Client, not a *gorm.DB.

Expected

For mongodb, the DI container should:

• take a *mongo.Database (derived from the mongoClient),
• call repository.NewMongo<Entity>Repository(...),
• and be wired into the Mongo main.go.

Notes / current state

• The Mongo repository now compiles (Update/Delete/FindAll implemented; unused import removed) — PR fix(db): driver-correct DSN + auto-migration so generated CRUD actually works (SQLite default was broken) #54.
• integrate no longer injects GORM wiring into the Mongo main.go (it would reference an undefined db) — PR fix(db): driver-correct DSN + auto-migration so generated CRUD actually works (SQLite default was broken) #54 leaves Mongo main.go untouched and prints a warning.
• What remains is a Mongo-specific DI container generator. The SQL drivers (postgres/mysql/sqlite/sqlserver) are verified working end-to-end (real CRUD).