Open chenfisher opened 7 years ago
Should a plain defdb
call assume the user wants a connection pool by default? Is leaving it out unless the user explicitly asks for it the best/most straightforward option, or should it be the default regardless?
In either case, I agree that the docs should be more explicit about this.
The docs states that
defdb
creates a connection pool but from looking at the code and from testing real DB interaction usingdefdb
it seems there's no connection pool.:make-pool
is missing from the spec.Either the doc should be changed or
defdb
should add the:make-pool true
to the spec