GORM’s context support, enabled by the WithContext
method, is a powerful feature that enhances the flexibility and control of database operations in Go applications. It allows for context management across different operational modes, timeout settings, and even integration into hooks/callbacks and middlewares. Let’s delve into these various aspects:
Режим одной сессии
Single session mode is appropriate for executing individual operations. It ensures that the specific operation is executed within the context’s scope, allowing for better control and monitoring.
db.WithContext(ctx).Find(&users) |
Continuous Session Mode
Continuous session mode is ideal for performing a series of related operations. It maintains the context across these operations, which is particularly useful in scenarios like transactions.
tx := db.WithContext(ctx) |
Context Timeout
Setting a timeout on the context passed to db.WithContext
can control the duration of long-running queries. This is crucial for maintaining performance and avoiding resource lock-ups in database interactions.
ctx, cancel := context.WithTimeout(context.Background(), 2*time.Second) |
Контекст в Hooks/Callbacks
The context can also be accessed within GORM’s hooks/callbacks. This enables contextual information to be used during these lifecycle events.
func (u *User) BeforeCreate(tx *gorm.DB) (err error) { |
Integration with Chi Middleware
GORM’s context support extends to web server middlewares, such as those in the Chi router. This allows setting a context with a timeout for all database operations within the scope of a web request.
func SetDBMiddleware(next http.Handler) http.Handler { |
Note: Setting the Context
with WithContext
is goroutine-safe. This ensures that database operations are safely managed across multiple goroutines. For more details, refer to the Session documentation in GORM.
Logger Integration
GORM’s logger also accepts Context
, which can be used for log tracking and integrating with existing logging infrastructures.
Refer to Logger documentation for more details.