Class for use when handling database rows
void DBRow (&DBTable table_object [, mixed primary_key_value])
This class is used for handling rows within a database table. table_object must be supplied and must be an initialised DBTable object. If supplied, primary_key_value will be used to fetch the corresponding row from the database (using DBRow::GetDetails) and store its details within the object upon instantiation.<database_table_column_name> (multiple; dynamic)
::ClearFields - Clear a DBRow object
::Delete - Delete a row from the database
::FillFromArray - Fill object properties from an array
::GetBinaryData - Retrieve binary data from the database
::GetDetails - Retrieve a row from the database
::HandleDataUpload - Handle uploaded data and store in database
::Insert - Insert a row into the database
::SetAuditNotes - Set descriptive notes for audit purposes
::SetAuditOwner - Set 'owner' for audit purposes
::Store - Store a row in the database, automatically determining whether to insert a new row or update an existing row
::Update - Update a row in the database
Hooks are intended for use by derived classes. To use hooks, simply set a property (named as below) to be the statement you want to execute, and it will be eval()'d at the appropriate time. For example, _Hook_Delete_pre is executed right at the start of the DBRow::Delete function. _Hook_Delete_post is executed right at the end of it.
_Hook_FetchIntoObject_pre (do NOT use $this-> in it)
_Hook_FetchIntoObject_post (do NOT use $this-> in it)
_Hook_Constructor_pre
_Hook_Constructor_post
_Hook_Delete_pre
_Hook_Delete_post
_Hook_GetDetails_pre
_Hook_GetDetails_post
_Hook_Insert_pre
_Hook_Insert_post
_Hook_Store_pre
_Hook_Store_post
_Hook_Update_pre
_Hook_Update_post
_skip_audit (set to TRUE to skip audit logging for actions on this object)
See also DBTable Class.
| You are here: Home > Documentation > DBRow Class |