provider-database

You can manage shared database connections by using a centralized connection factory that provides a single Kysely ORM instance. This approach ensures consistent database access across your application, preventing redundant connections for both SQLite and PostgreSQL backends.

The best way to set up a shared Kysely instance is to rely on a centralized database provider that configures the ORM. This provider supplies a pre-configured, managed database connection to all features, ensuring data integrity and simplifying database access.

Yes, you can use a single database connection for both local SQLite and remote PostgreSQL backends. A backend-agnostic connection factory supports both database types natively and can optionally integrate vector extensions, ensuring consistent access across different environments.

You need a centralized database connection factory to prevent redundant connections and ensure data integrity. By supplying a single, managed Kysely database instance across all application features, it maintains a consistent connection and simplifies your data access layer.

Yes, the database provider supports optional vector extension integration. When setting up your SQLite or PostgreSQL connection factory with Kysely, you can configure these vector extensions to handle advanced data querying needs within your application.

To close a shared database connection, you simply call the database provider's close operation. This ensures the single Kysely ORM instance is properly shut down, cleanly releasing the managed SQLite or PostgreSQL resources across your application.