KexiDB::AlterTableHandler::FieldActionBase Class Reference
#include <alter.h>
Inheritance diagram for KexiDB::AlterTableHandler::FieldActionBase:
Public Member Functions | |
| FieldActionBase (const TQString &fieldName, int uid) | |
| FieldActionBase (bool) | |
| TQString | fieldName () const |
| int | uid () const |
| void | setFieldName (const TQString &fieldName) |
Public Member Functions inherited from KexiDB::AlterTableHandler::ActionBase | |
| ActionBase (bool null=false) | |
| ChangeFieldPropertyAction & | toChangeFieldPropertyAction () |
| RemoveFieldAction & | toRemoveFieldAction () |
| InsertFieldAction & | toInsertFieldAction () |
| MoveFieldPositionAction & | toMoveFieldPositionAction () |
| bool | isNull () const |
| virtual TQString | debugString (const DebugOptions &debugOptions=DebugOptions()) |
| void | debug (const DebugOptions &debugOptions=DebugOptions()) |
Protected Attributes | |
| int | m_fieldUID |
Additional Inherited Members | |
Protected Member Functions inherited from KexiDB::AlterTableHandler::ActionBase | |
| void | setAlteringRequirements (int alteringRequirements) |
| int | alteringRequirements () const |
| virtual void | updateAlteringRequirements () |
| virtual void | simplifyActions (ActionDictDict &fieldActions) |
| virtual bool | shouldBeRemoved (ActionDictDict &fieldActions) |
| virtual tristate | updateTableSchema (TableSchema &table, Field *field, TQMap< TQString, TQString > &fieldMap) |
Detailed Description
Abstract base class used for implementing table field-related actions.
Constructor & Destructor Documentation
◆ FieldActionBase() [1/2]
| AlterTableHandler::FieldActionBase::FieldActionBase | ( | const TQString & | fieldName, |
| int | uid | ||
| ) |
◆ FieldActionBase() [2/2]
| AlterTableHandler::FieldActionBase::FieldActionBase | ( | bool | ) |
◆ ~FieldActionBase()
|
virtual |
Member Function Documentation
◆ fieldName()
|
inline |
◆ setFieldName()
|
inline |
◆ uid()
|
inline |
- Returns
- field's unique identifier This id is needed because in the meantime there can be more than one field sharing the same name, so we need to identify them unambiguously. After the (valid) altering is completed all the names will be unique.
Example scenario when user exchanged the field names:
- At the beginning: [field A], [field B]
- Rename the 1st field to B: [field B], [field B]
- Rename the 2nd field to A: [field B], [field A]
Member Data Documentation
◆ m_fieldUID
|
protected |
The documentation for this class was generated from the following files:

Public Member Functions inherited from