Does renaming a field in Bknd cause data loss?

Yes, Bknd treats renames as dropping the old column and creating a new one. This skill provides a multi-step migration pattern to move data safely to the new field before dropping the old one.

Can I change a field to 'required' if it already has null values?

No, the database sync will fail because of existing null constraints. You must first update all null records with a default value via a script before adding the .required() constraint to your schema.

When should I use the --force flag with npx bknd sync?

Use the --force flag only when you are ready to apply destructive changes, such as dropping columns or entities, and after you have verified the impact using a dry run and backed up your data.

What is the best way to handle incompatible type changes?

The safest approach is to create a new field with the target type, run a migration script to transform and copy the data from the old field, and then remove the old field in a subsequent sync.

Bknd Schema Modification

Name: Bknd Schema Modification
Author: cameronapak

bycameronapak

•

Database Management

Manages schema changes in Bknd apps including entity renaming, field type updates, and safe data migration workflows.

About

This skill provides specialized guidance for modifying existing database schemas within the Bknd.io ecosystem. It addresses the critical distinction between destructive and non-destructive changes, offering step-by-step patterns for renaming entities and fields without data loss. Whether working in UI or Code mode, the skill helps developers navigate complex tasks like tightening constraints on existing data, changing field types, and executing the sync workflow to ensure production database integrity and minimize deployment risks.

Key Features

Explains the npx bknd sync workflow and preview options
Distinguishes between destructive and non-destructive schema changes
1 GitHub stars
Includes a reusable migration script template for complex transitions
Provides safe data migration patterns for renaming entities and fields
Guides users through changing field types and updating constraints safely

Use Cases

Converting an existing text field to a numeric type with data transformation
Renaming a core database entity while preserving existing production data
Safely adding 'required' or 'unique' constraints to columns that already contain data

About

Key Features

Explains the npx bknd sync workflow and preview options
Distinguishes between destructive and non-destructive schema changes
1 GitHub stars
Includes a reusable migration script template for complex transitions
Provides safe data migration patterns for renaming entities and fields
Guides users through changing field types and updating constraints safely

Use Cases

Converting an existing text field to a numeric type with data transformation
Renaming a core database entity while preserving existing production data
Safely adding 'required' or 'unique' constraints to columns that already contain data