Kexi/Plugins/Tables/Backups: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Design page for task: '''"Add support for table backup"'''. | |||
*Started: [[User:Jstaniek|Jstaniek]] September 2012 | |||
*{{wish|306270}} | |||
*Target: 2.6.0 | |||
__TOC__ | |||
==Rationale== | |||
Support for table backups would be a simple but useful feature for many reasons. | Support for table backups would be a simple but useful feature for many reasons. | ||
Before doing data edit user may decide create backup of relevant table(s). It may be faster and lighter than backing up entire database. | Before doing data edit user may decide create backup of relevant table(s). It may be faster and lighter than backing up entire database. | ||
==Other uses== | |||
Another case can be user editing schema for table that already contains data. | Another case can be user editing schema for table that already contains data. | ||
| Line 9: | Line 16: | ||
We'll have to test the feature for some extended time, so backing up by default is good. Moreover tables are not that big considering performance of the current hardware. | We'll have to test the feature for some extended time, so backing up by default is good. Moreover tables are not that big considering performance of the current hardware. | ||
==Details== | |||
Proposed backup should be available within Tools, as a Backup Data button. There should be also Show Backups button to show existing backups for current object (if it's a table), enabling retrieving table from backup. | Proposed backup should be available within Tools, as a Backup Data button. There should be also Show Backups button to show existing backups for current object (if it's a table), enabling retrieving table from backup. | ||
| Line 15: | Line 23: | ||
Physically, table backups can be created by deep-copying a table to different name, preferable is kexi__**** so the backup is hidden even in previous Kexi versions. | Physically, table backups can be created by deep-copying a table to different name, preferable is kexi__**** so the backup is hidden even in previous Kexi versions. | ||
==Extensions== | |||
Backing up any objects and entire database. | |||
Revision as of 22:26, 4 September 2012
Design page for task: "Add support for table backup".
- Started: Jstaniek September 2012
- Wish #306270
- Target: 2.6.0
Rationale
Support for table backups would be a simple but useful feature for many reasons. Before doing data edit user may decide create backup of relevant table(s). It may be faster and lighter than backing up entire database.
Other uses
Another case can be user editing schema for table that already contains data.
I propose to also backup table automatically before performing schema alteration using the new more powerful Alter Table feature. We'll have to test the feature for some extended time, so backing up by default is good. Moreover tables are not that big considering performance of the current hardware.
Details
Proposed backup should be available within Tools, as a Backup Data button. There should be also Show Backups button to show existing backups for current object (if it's a table), enabling retrieving table from backup.
Backups shall be indexed by backup date and optional textual description.
Physically, table backups can be created by deep-copying a table to different name, preferable is kexi__**** so the backup is hidden even in previous Kexi versions.
Extensions
Backing up any objects and entire database.