Abstract class to do data save/delete operations for a particular data type (such as user, thread, post etc.)
Located in /includes/class_dm.php (line 20)
Class | Description |
---|---|
![]() |
DataManager for manipulating discussions. |
![]() |
Class to do data save/delete operations for PT issue votes. |
![]() |
Class to do data save/delete operations for MODERATORS |
![]() |
Class to do data save/delete operations for ADMINISTRATORS |
![]() |
Class to do data save/delete operations for Social Group Categories |
![]() |
Base data manager for blogs and blogtexts. Uninstantiable. |
![]() |
vB_DataManager_Avatar vB_DataManager_ProfilePic Abstract class to do data save/delete operations for Userpics. |
![]() |
Class to do data save/delete operations for Social Groups |
![]() |
Class to do data save/delete operations for Social Groups |
![]() |
Class to do data save/delete operations for PT milestones. |
![]() |
Class to do data save/delete operations for profile messages |
![]() |
Class to do data save/delete operations for THREAD RATINGS |
![]() |
Class to do data save/delete operations for PT issue changes. |
![]() |
Class to do data save/delete operations for PRIVATE MESSAGES Note: you may only do inserts with this class. |
![]() |
Class to do data save/delete operations for pollvotes |
![]() |
Class to do data save/delete operations for deleted threads/posts |
![]() |
Class to do data save/delete operations for layouts |
![]() |
Class to do data save/delete operations for PT issue assignments. |
![]() |
Class to do data save/delete operations for PT issue petitions. |
![]() |
Class to do data save/delete operations for FORUMS |
![]() |
Class to do data save/delete operations for blog users |
![]() |
Class to do data save/delete operations for Blog ratings |
![]() |
Class to do data save/delete operations for widgets for the admincp |
![]() |
Class to do data save/delete operations for ANNOUNCEMENTS |
![]() |
Class to do data save/delete operations for EVENTS |
![]() |
Class to do data save/delete operations for RSS Feeds |
![]() |
Class to do data save/delete operations for PT issue notes (generic). |
![]() |
Class to do data save/delete operations for profile messages |
![]() |
Class to do data save/delete operations for PT issue reports. |
![]() |
Class to do data save/delete operations for PT issue assignments. |
![]() |
Class to do data save/delete operations for thread prefix sets |
![]() |
Abstract class to do data save/delete operations for ATTACHMENTS. |
![]() |
Class to do data save/delete operations for profile messages |
![]() |
Class to do data save/delete operations for PT issue types. |
![]() |
Class to do data operations for Categories |
![]() |
Class to do data operations for Categories |
![]() |
Base data manager for threads and posts. Uninstantiable. |
![]() |
Class to do data save/delete operations for PT issue statuses. |
![]() |
Class to do data save/delete operations for PT issue subscriptiosn. |
![]() |
Class to do data save/delete operations for PT issues. |
![]() |
Class to do data save/delete operations for POLLS |
![]() |
Class to do data save/delete operations for StyleVarDefinitions. |
![]() |
Abstract class to do data save/delete operations for StyleVar. |
![]() |
Class to do data save/delete operations for blog users |
![]() |
Class to do data save/delete operations for infractions |
![]() |
vB_DataManager_SocialGroupIcon Class to do data save/delete operations for SocialGroupIcons. |
![]() |
Class to do data save/delete operations for picture comments |
![]() |
Class to do data save/delete operations for albums |
![]() |
Class to do data save/delete operations for thread prefixes |
![]() |
Class to do data save/delete operations for USERS |
![]() |
Class to do data save/delete operations for blog users |
Array of field names that are bitfields, together with the name of the variable in the registry with the definitions.
For example: var $bitfields = array('options' => 'bf_misc_useroptions', 'permissions' => 'bf_misc_moderatorpermissions')
Condition to be used in SQL query - if empty, an INSERT query will be performed
Condition template for update query This is for use with sprintf(). First key is the where clause, further keys are the field names of the data to be used.
The vBulletin database object
Array to store any errors encountered while building data
The error handler for this object
Array to store existing data
Callback to execute just before an error is logged.
Hook for post_delete.
Hook for post_save.
Hook for pre_save.
Hook for constructor.
Array to store information
Will contain the temporary verification function for each field
This variable prevents the pre_save() method from being called more than once.
In some classes, it is helpful to explicitly call pre_save() before calling save as additional checks are done. This variable is used to prevent pre_save() from being executed when save() is called. If null, pre_save() has yet to be called; else, it is the return value of pre_save().
Array to store the names for fields that will be taking raw SQL
The vBulletin registry object
Array to store the names of fields that have been sucessfully set
Default table to be used in queries
Array of field names that are valid for this data object
Each array element has the field name as its key, and then a three element array as the value. These three elements are used as follows: FIELD 0 (VF_TYPE) - This specifies the expected data type of the field, and draws on the data types defined for the vB_Input_Cleaner class FIELD 1 (VF_REQ) - This specified whether or not the field is REQUIRED for a valid INSERT query. Options include REQ_NO, REQ_YES and REQ_AUTO, which is a special option, indicating that the value of the field is automatically created FIELD 2 (VF_CODE) - This contains code to be executed as a lamda function called as 'function($data, $dm)'. Alternatively, the value can be VF_METHOD, in which case, $this->verify_{$fieldname} will be called.
Constructor - checks that the registry object has been passed correctly.
Checks through the required fields for this object and ensures that all required fields have a value
Generates the SQL to delete a record from a database table, then executes it
Creates and runs an INSERT query to save the data from the object into the database
Creates and runs an INSERT query to save the data from the object into the database
Creates and runs an UPDATE query to save the data from the object into the database
Deletes the specified data item from the database
Takes valid data and sets it as part of the data to be saved
Unsets a values that has already been set
Shows an error message and halts execution - use this in the same way as print_stop_message();
Fetches info about the current data object - if a new value is set, it returns this, otherwise it will return the existing data
Builds an INSERT/REPLACE query
Builds an UPDATE query
Check if the DM currently has errors. Will kill execution if it does and $die is true.
Additional data to update after a delete call (such as denormalized values in other tables).
Additional data to update after a save call (such as denormalized values in other tables).
In batch updates, is executed for each record updated.
Additional data to update after a save call (such as denormalized values in other tables).
In batch updates, is executed once after all records are updated.
Additional data to update before a delete call (such as denormalized values in other tables).
Any checks to run immediately before saving. If returning false, the save will not take place.
Saves the data from the object into the specified database tables
Sets the supplied data to be part of the data to be saved. Use setr() if a reference to $value is to be passed
Sets the supplied data to be part of the data to be saved
Rather like set(), but sets reference to data into the $this->info array instead
Sets a bit in a bitfield
Sets the condition to be used in WHERE clauses, based upon the $this->existing data and the $this->condition_constuct condition template.
Sets the error handler for the object
Sets the existing data
Sets the function to call on an error.
Rather like set(), but sets data into the $this->info array instead. Use setr_info if $value if a reference to value is to be passed
Strips empty BB code from the entire message except inside PHP/HTML/Noparse tags.
Callback function for strip_empty_bbcode.
Verifies that the supplied data is one of the fields used by this object
Also ensures that the data is of the correct type, and attempts to correct errors in the supplied data.
Verifies that a variable is a comma-separated list of integers
Verifies a date array as a valid unix timestamp
Verifies that an email address is valid
Verifies the number of images in the post text. Call it from pre_save() after pagetext/allowsmilie has been set
Verifies an IP address - currently only works with IPv4
Verifies that a hyperlink is valid
Creates a valid string of comma-separated integers
Verifies that a string is an MD5 string
Verifies that a string is not empty
Verifies that an integer is greater than zero
Verifies that an integer is greater than zero or the special value -1 this rule matches a fair number of id columns
Basic options to perform on all pagetext type fields
Verifies that input is a serialized array (or force an array to serialize)
Verifies that a variable is a space-separated list of integers
Verifies that the specified user exists
Verifies that the provided username is valid, and attempts to correct it if it is not valid
Documentation generated on Tue, 26 Jan 2010 15:15:08 -0600 by phpDocumentor 1.4.3