Lovable: Test Database Changes in a Draft
Lovable now gives each draft on a project with the built-in backend its own backend filled with example data. Users can test a change that stores new information, such as a new form field, without touching the live app. When a draft is accepted, Lovable applies the change to the live database before publishing and leaves the test data behind.
Key Takeaways
- Each draft on a project with the built-in backend now gets its own backend, separate from the live database.
- The draft backend is pre-filled with example data, so changes can be tried against realistic content.
- Changes such as a new form field can be tested end to end without affecting the live app.
- Accepting a draft applies the data change to the live database before publishing, so the schema and the app ship together.
- Test data is left behind in the draft and never reaches the live database.
- The feature lowers the risk of data model changes, which were previously harder to try safely.
A separate backend for every draft
Lovable now gives a draft its own backend when a project uses the built-in backend. That backend comes filled with example data, so a draft no longer shares the live database while changes are being tried out.
Test data changes safely
The new setup matters most for changes that store new information. A new form field is a typical case: inside the draft, a user can submit the form, see the data saved, and check that the app behaves correctly, all without changing anything in the live app or its real records.
What happens when a draft is accepted
Accepting a draft applies the change to the live database before the app is published. The test data created in the draft stays behind in the draft's backend, so the live database receives the structural change but not the experiments used to verify it. This gives users a safer path from trying a data change to shipping it.