rwsdk-database-do

To set up SQLite Durable Objects, create migration files, define a database instance, implement a Durable Object class, export it from your worker, and update wrangler.toml to bind the object for type-safe queries.

Database migrations for SQLite Durable Objects are managed by defining schema changes in a migrations file, which allows safe rollback paths and automatic schema evolution across isolated Durable Object instances.

Yes, you can perform joins and CRUD operations without runtime schema hints by leveraging Kysely-powered typings that are automatically inferred directly from your migration files.

Kysely works with SQLite Durable Objects to provide type-safe database queries by inferring schema types directly from migrations, eliminating the need for separate code generation steps.

The best way to seed initial data into isolated SQLite Durable Objects is by using the built-in seeding and maintenance features provided during development and deployment to manage initial records.

Using migration-driven schema inference instead of code generation streamlines development by automatically typing your queries through migrations, ensuring your database schema stays synchronized with your code safely.