Deleting your database change history is permanent and can't be undone. It deletes all database backups, so you can no longer restore your database to any earlier state. By continuing, you confirm that you understand the consequences and accept responsibility for this action.
Bubble lets you delete all of your database change history. This article explains what that means, when it can make sense, and how to do it.
What deleting the change history means
Your app's two databases, development and live, are both backed up continuously, every time a change is made. This is often called real-time backup, and it lets you restore a database to any moment in the past, down to the second. How far back you can go depends on your app's plan.
The change history is the record of these backups. When you delete it, you can no longer restore the database to any earlier state. Real-time backups start again right away, so your earliest possible restore point becomes the moment just after the deletion.
When to delete the change history
In most cases, there's no reason to delete your change history. It's there so that you can restore your database quickly if something goes wrong, without having to export or import any data.
That said, there are a few situations where it can make sense:
Situation | Why deleting the change history helps |
You need to remove data permanently | Deleting records isn't enough on its own, since they can still be restored from the change history. Deleting the history makes sure the data can't be brought back. |
You have test data you're sure you want gone for good | For example, if one or both databases hold test data that you never want to restore. |
Your app is on the Enterprise plan | Deleting the change history can free up storage space. |
You want to improve database performance | Less data may give a slight speed boost for very large databases. The gain is usually small, though, and losing your backups is a significant downside, so we don't recommend deleting the history for performance alone. |
How to delete the database change history
1. Open the App data section
In the editor, go to the Data tab (see Key terms) and open the App data section.
2. Select the right database
Check which database you're viewing in the header above the data table. To switch, click Switch to live database or Switch to development database in the upper right corner.
The change history is only deleted for the database you're viewing, so take a moment to make sure it's the right one.
3. Open the delete option
Click Copy and restore database, then select Delete all change history from the dropdown.
4. Confirm
Follow the instructions in the popup, then click Delete history. Depending on the size of your database, deleting the change history can take a few minutes.
FAQ: Deleting database change history
Does deleting the change history affect both databases?
Does deleting the change history affect both databases?
No. It only affects the database you're viewing in the App data section. See How to delete the database change history for how to switch between them.
I deleted the change history by accident. Can I get it back?
I deleted the change history by accident. Can I get it back?
No. Deleting the change history is permanent and can't be undone. Before you confirm, check that you've selected the right database and that you understand the consequences.
Does deleting the change history turn off real-time backups?
Does deleting the change history turn off real-time backups?
No. Real-time backups start again right after the deletion. You can restore to any point after the deletion, but not before it.
Can I choose which data to delete, for example only one data type?
Can I choose which data to delete, for example only one data type?
No. Deleting the change history affects all data types in that database.
Key terms
Data tab: The Data tab is where you view and manage your app's database, files, and option sets.
Reference: The Data tab