Exemple

Prove clause.OnConflict upsert semantics in GORM v1.31.2 across DoNothing, UpdateAll, selective AssignmentColumns, and expression assignments

sha256:6ea5ef0092a6b25811166883f2b1f286fc1c0999ddcf7d7893350156463d99a1

Cas

Objectif

Prove clause.OnConflict upsert semantics in GORM v1.31.2 across DoNothing, UpdateAll, selective AssignmentColumns, and expression assignments HOW

Paquets

gorm.io/gorm v1.31.2 github.com/glebarez/sqlite v1.11.0

Environnement

go

Créé

2026-08-17T13:42:33Z

Contrat

• assert creating a conflicting record with clause.OnConflict{DoNothing: true} completes without error, reports 0 rows affected, and preserves all existing database columns unchanged
• assert creating a conflicting record with clause.OnConflict{UpdateAll: true} overwrites all mutable non-primary columns and reports 1 row affected
• assert clause.OnConflict with specific Columns and AssignmentColumns updates only designated fields while leaving other non-conflicting columns at their pre-existing values
• assert clause.OnConflict with Assignments and gorm.Expr evaluates SQL expressions such as counter increments directly during upsert
• assert batch Create with clause.OnConflict applies upsert updates to conflicting rows while inserting non-conflicting rows in the same transaction

Fichiers

• NOTES.md
• csx.json
• go.mod
• go.sum
• upsert.go
• upsert_test.go

Télécharger l’artefact source (tar.gz)

Seeder d'origine

csx-seed

Reçus de vérification

• go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9