Kexi/Plugins/Tables/Simple alter table: Difference between revisions

From KDE Community Wiki
< Kexi‎ | Plugins‎ | Tables
Line 18: Line 18:
*triggers name change in property editor, so:
*triggers name change in property editor, so:
**A: if name changed, ask for accepting name change:
**A: if name changed, ask for accepting name change:
***if accepted go to ''Name change'' section
***if accepted go to [[#Name change]] section
***if not accepted, revert the recent name change and go to B
***if not accepted, revert the recent name change and go to B
**B: else, do nothing, caption should be saved on Save action
**B: else, do nothing, caption should be saved on Save action


===Name change===
===Name change===
*can happen after change of caption (see Caption rename)
*can happen after:
*can happen after changed ''name'' value in the property editor
**change of caption (see Caption rename)
**or ''name'' value changes in the property editor
*request instant applying
*request instant applying
*Algorithm:
*Algorithm:
Line 36: Line 37:


===Field removing===
===Field removing===
*triggered by "Delete Record" action, available in context menu
*request instant applying
*Algorithm:


===Field removing===
===Field removing===

Revision as of 12:53, 2 September 2012

Design page for task: Simple approach to fulfill "Add support for alter table's design without losing data" wish.

Rationale

Approach when modification to table schema is saved directly after user performed it is much easier than full alter table tired in Kexi 1.x and never delivered.

Analysis

  • Altering some physical properties would require immediate saving of the design but will not remove all the data.
  • Other properties (for which KexiDB::isExtendedTableFieldProperty() return true) can be modified without altering any data.

Alter actions

This section publishes details on particular actions of table altering.

Caption rename

  • triggers name change in property editor, so:
    • A: if name changed, ask for accepting name change:
      • if accepted go to #Name change section
      • if not accepted, revert the recent name change and go to B
    • B: else, do nothing, caption should be saved on Save action

Name change

  • can happen after:
    • change of caption (see Caption rename)
    • or name value changes in the property editor
  • request instant applying
  • Algorithm:
    • if name is duplicated, display info and abort
    • ALTER TABLE available: send to the backend
    • ALTER TABLE not available:
      • Create full table copy with all columns but with one column renamed
      • Copy all records to the new table
      • Drop the original table
      • Rename table to the original name

Field removing

  • triggered by "Delete Record" action, available in context menu
  • request instant applying
  • Algorithm:


Field removing

Fields reordering

Field inserting

Requirements

  • Full data safety
    • It's better to warn and request data removal than claiming it is not necessary and then doing that
    • Enclose operations within transactions

Hints

  • Table rename in SQLite: ALTER TABLE RENAME TO...
  • Full table copy in SQLite: CREATE TABLE copy AS SELECT * FROM t;

Links