Is there a way to control how many db connections ormlite can open at one time? Rider was complaining it was opening 12 connections at the same time and I didn’t know if that could be controlled or just ignored?
OrmLite does not control or maintain a pool of connections, it opens a connection when it’s resolved from the DB and returns it back to the underlying ADO .NET Provider when its disposed.
Most ADO .NET Providers use a backing connection pool which it manages, you’ll need to consult their docs to learn about how it manages its connection pool and which of their behaviors can be tweaked.