Interface DatabasePoolOptions

If true, enable SQL extension loading for the duration of connectionSetup only; it is revoked before the connection is admitted to the pool. User operations can never call load_extension() in either authorizer mode.

Whether user SQL may create connection-local state.

Number of physical SQLite connections to open. Multiple connections let reads overlap, but SQLite still permits only one writer at a time.

In-memory and temporary databases are private to one connection, so :memory:, an empty location, and URI locations with mode=memory require exactly one.

Ordered statements run on every physical connection before open() resolves. Each must be safe to replay independently per connection, so use it for connection configuration rather than schema migrations. A failure rejects open() and closes every connection opened so far.

If true, return SQLite integers as bigint. With the default false, an integer outside the safe JavaScript range rejects the call rather than silently losing precision.

If true, return each row as an array of values instead of an object. Arrays preserve every column of a result that contains duplicate column names.