goSnowFlake | 一个实现 Twitter SnowFlake 算法 的 Go 分布式 UID 生成器.A threadsafe | Theme library

DB maintains a pool of connections. Each connection in the pool will have a unique session ID. From the documentation:

DB is a database handle representing a pool of zero or more underlying connections. It's safe for concurrent use by multiple goroutines.

The sql package creates and frees connections automatically; it also maintains a free pool of idle connections.

You have a couple options for bypassing the default behavior of cycling through the pool of connections:

1. Obtain a specific Conn instance from the connection pool using DB.Conn(). The documentation specifically states:

   Queries run on the same Conn will be run in the same database session.

2. Modify the connection pool parameters using DB.SetMaxOpenConns().

   I suspect that setting this to 1 will also obtain the desired behavior. However, this introduces scalability/concurrency concerns that are addressed by having a connection pool in the first place.

Note, I'm not familiar with the Snowflake driver in particular. There may be other options that the driver supports.