Update: Difference between revisions
No edit summary |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
The update action is used for saving changes to an existing record. | The update action is used for saving changes to an existing record. | ||
The standard handler class for the update action of a node is the | The standard handler class for the update action of a node is the [[atkUpdateHandler]]. | ||
This handler saves an existing record to the database. The data is retrieved from the postvars. This is the action that follows an [[edit|'edit']] action. The 'edit' action draws the edit form, the 'update' action saves the data to the database. | This handler saves an existing record to the database. The data is retrieved from the postvars. This is the action that follows an [[edit|'edit']] action. The 'edit' action draws the edit form, the 'update' action saves the data to the database. | ||
Validation of the record is performed before storage. If validation fails, the edit handler is invoked again. | Validation of the record is performed before storage. If validation fails, the edit handler is invoked again. | ||
Latest revision as of 13:26, 12 February 2010
|
ATK Action Handler: update
|
The update action is used for saving changes to an existing record.
The standard handler class for the update action of a node is the atkUpdateHandler.
This handler saves an existing record to the database. The data is retrieved from the postvars. This is the action that follows an 'edit' action. The 'edit' action draws the edit form, the 'update' action saves the data to the database.
Validation of the record is performed before storage. If validation fails, the edit handler is invoked again.