샘플

Keep a tenant scope from being bypassed by an ungrouped Or while inspecting GORM DryRun SQL

sha256:9ff4648d7bd88a17effda2a1b227607fcfea1c19d4ce72eebc4868f0dd20406e

케이스

목표

Keep a tenant scope from being bypassed by an ungrouped Or while inspecting GORM DryRun SQL HOW

패키지

gorm.io/gorm v1.31.2 gorm.io/driver/sqlite v1.6.0

환경

go 1.26

생성일

2026-08-17T01:32:02Z

흔히 이렇게 알고 있다

Calling Scopes(Tenant(id)) before Where(...).Or(...) keeps the tenant predicate in force for both OR branches because the scope appears first in the chain.

이 샘플의 작성자가 여기서 개발자나 모델이 기대할 법한 내용으로 적어둔 것이다. 아래 계약이 실제로 실행된 것이다.

컨트랙트

• assert Scopes(Tenant(7)).Where("active = ?", true).Or("role = ?", "admin") generates WHERE active = ? OR role = ? AND tenant_id = ?, so SQL precedence allows active rows from other tenants
• assert the ungrouped statement binds [true, "admin", uint(7)] in that order, proving the lazily executed tenant scope is appended after the chained conditions
• assert passing Where("active = ?", true).Or("role = ?", "admin") as one nested Where condition generates WHERE (active = ? OR role = ?) AND tenant_id = ? with the same bind values
• assert DryRun Find executes no SQL against database/sql; only the official SQLite dialector's required select sqlite_version() initialization probe reaches the in-process stub

파일

• NOTES.md
• csx.json
• go.mod
• go.sum
• scope.go
• scope_test.go

검증된 아티팩트 내려받기 (tar.gz) — 컨트랙트가 실제로 실행된 바로 그 바이트

오리진 시더

csx-seed

검증 영수증

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