vB_DataManagerAbstract 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 |
|---|---|
vB_DataManager_Discussion
|
DataManager for manipulating discussions. |
vB_DataManager_Pt_IssueVote
|
Class to do data save/delete operations for PT issue votes. |
vB_DataManager_Moderator
|
Class to do data save/delete operations for MODERATORS |
vB_DataManager_Admin
|
Class to do data save/delete operations for ADMINISTRATORS |
vB_DataManager_SocialGroupCategory
|
Class to do data save/delete operations for Social Group Categories |
vB_DataManager_Blog_Abstract
|
Base data manager for blogs and blogtexts. Uninstantiable. |
vB_DataManager_Userpic
|
vB_DataManager_Avatar vB_DataManager_ProfilePic Abstract class to do data save/delete operations for Userpics. |
vB_DataManager_SocialGroup
|
Class to do data save/delete operations for Social Groups |
vB_DataManager_SocialGroupMember
|
Class to do data save/delete operations for Social Groups |
vB_DataManager_Pt_Milestone
|
Class to do data save/delete operations for PT milestones. |
vB_DataManager_VisitorMessage
|
Class to do data save/delete operations for profile messages |
vB_DataManager_ThreadRate
|
Class to do data save/delete operations for THREAD RATINGS |
vB_DataManager_Pt_IssueChange
|
Class to do data save/delete operations for PT issue changes. |
vB_DataManager_PM
|
Class to do data save/delete operations for PRIVATE MESSAGES Note: you may only do inserts with this class. |
vB_DataManager_PollVote
|
Class to do data save/delete operations for pollvotes |
vB_DataManager_DeletionLog
|
Class to do data save/delete operations for deleted threads/posts |
vB_DataManager_Cms_Layout
|
Class to do data save/delete operations for layouts |
vB_DataManager_Pt_IssueAssign
|
Class to do data save/delete operations for PT issue assignments. |
vB_DataManager_Pt_IssuePetition
|
Class to do data save/delete operations for PT issue petitions. |
vB_DataManager_Forum
|
Class to do data save/delete operations for FORUMS |
vB_DataManager_Blog_TrackBack
|
Class to do data save/delete operations for blog users |
vB_DataManager_Blog_Rate
|
Class to do data save/delete operations for Blog ratings |
vB_DataManager_vBCms_Widget
|
Class to do data save/delete operations for widgets for the admincp |
vB_DataManager_Announcement
|
Class to do data save/delete operations for ANNOUNCEMENTS |
vB_DataManager_Event
|
Class to do data save/delete operations for EVENTS |
vB_DataManager_RSSFeed
|
Class to do data save/delete operations for RSS Feeds |
vB_DataManager_Pt_IssueNote
|
Class to do data save/delete operations for PT issue notes (generic). |
vB_DataManager_GroupMessage
|
Class to do data save/delete operations for profile messages |
vB_DataManager_Pt_IssueReport
|
Class to do data save/delete operations for PT issue reports. |
vB_DataManager_Pt_Project
|
Class to do data save/delete operations for PT issue assignments. |
vB_DataManager_PrefixSet
|
Class to do data save/delete operations for thread prefix sets |
vB_DataManager_AttachData
|
Abstract class to do data save/delete operations for ATTACHMENTS. |
vB_DataManager_Blog_Custom_Block
|
Class to do data save/delete operations for profile messages |
vB_DataManager_Pt_IssueType
|
Class to do data save/delete operations for PT issue types. |
vB_DataManager_Tag
|
Class to do data operations for Categories |
vB_DataManager_category
|
Class to do data operations for Categories |
vB_DataManager_ThreadPost
|
Base data manager for threads and posts. Uninstantiable. |
vB_DataManager_Pt_IssueStatus
|
Class to do data save/delete operations for PT issue statuses. |
vB_DataManager_Pt_IssueSubscribe
|
Class to do data save/delete operations for PT issue subscriptiosn. |
vB_DataManager_Pt_Issue
|
Class to do data save/delete operations for PT issues. |
vB_DataManager_Poll
|
Class to do data save/delete operations for POLLS |
vB_DataManager_StyleVarDefn
|
Class to do data save/delete operations for StyleVarDefinitions. |
vB_DataManager_StyleVar
|
Abstract class to do data save/delete operations for StyleVar. |
vB_DataManager_Blog_Category
|
Class to do data save/delete operations for blog users |
vB_DataManager_Infraction
|
Class to do data save/delete operations for infractions |
vB_DataManager_SocialGroupIcon
|
vB_DataManager_SocialGroupIcon Class to do data save/delete operations for SocialGroupIcons. |
vB_DataManager_PictureComment
|
Class to do data save/delete operations for picture comments |
vB_DataManager_Album
|
Class to do data save/delete operations for albums |
vB_DataManager_Prefix
|
Class to do data save/delete operations for thread prefixes |
vB_DataManager_User
|
Class to do data save/delete operations for USERS |
vB_DataManager_Blog_User
|
Class to do data save/delete operations for blog users |
integer
db_delete
(string $tableprefix, string $table, [string $condition = ''], [boolean $doquery = true])
integer
db_insert
(string $tableprefix, string $table, [boolean $doquery = true], [bool $replace = false])
boolean
db_update
(string $tableprefix, string $table, [string $condition = ''], [boolean $doquery = true], [mixed $delayed = false], [boolean $affected_rows = false])
string
fetch_insert_sql
(string $tableprefix, string $table, [bool $replace = false], [bool $ignore = false])
mixed
save
([boolean $doquery = true], [mixed $delayed = false], [bool $affected_rows = false], [bool $replace = false], [bool $ignore = false])
boolean
set
(string $fieldname, mixed $value, [boolean $clean = true], [boolean $doverify = true], [string $table = null])
boolean
setr
(string $fieldname, mixed &$value, [boolean $clean = true], [boolean $doverify = true])
bool
verify_image_count
([ $pagetext = 'pagetext'], [ $allowsmilie = 'allowsmilie'], [ $parsetype = 'nonforum'], [ $table = null])
array
$bitfields
= array() (line 44)
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')
string
$condition
= null (line 114)
Condition to be used in SQL query - if empty, an INSERT query will be performed
array
$condition_construct
= array('dataid = %1$d', 'dataid') (line 129)
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.
vB_Database
$dbobject
= null (line 72)
The vBulletin database object
array
$errors
= array() (line 86)
Array to store any errors encountered while building data
string
$error_handler
= ERRTYPE_STANDARD (line 93)
The error handler for this object
array
$existing
= array() (line 100)
Array to store existing data
callback
$failure_callback
= null (line 136)
Callback to execute just before an error is logged.
string
$hook_delete
= 'data_delete' (line 175)
Hook for post_delete.
string
$hook_postsave
= 'data_postsave' (line 168)
Hook for post_save.
string
$hook_presave
= 'data_presave' (line 161)
Hook for pre_save.
string
$hook_start
= 'data_start' (line 154)
Hook for constructor.
array
$info
= array() (line 107)
Array to store information
function
$lamda
= null (line 79)
Will contain the temporary verification function for each field
null|bool
$presave_called
= null (line 147)
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
$rawfields
= array() (line 58)
Array to store the names for fields that will be taking raw SQL
vB_Registry
$registry
= null (line 65)
The vBulletin registry object
array
$setfields
= array() (line 51)
Array to store the names of fields that have been sucessfully set
string
$table
= 'default_table' (line 121)
Default table to be used in queries
array
$validfields
= array() (line 36)
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 vB_DataManager (line 183)
Constructor - checks that the registry object has been passed correctly.
check_required (line 560)
Checks through the required fields for this object and ensures that all required fields have a value
db_delete (line 817)
Generates the SQL to delete a record from a database table, then executes it
db_insert (line 720)
Creates and runs an INSERT query to save the data from the object into the database
db_insert_ignore (line 772)
Creates and runs an INSERT query to save the data from the object into the database
db_update (line 626)
Creates and runs an UPDATE query to save the data from the object into the database
delete (line 978)
Deletes the specified data item from the database
do_set (line 545)
Takes valid data and sets it as part of the data to be saved
do_unset (line 526)
Unsets a values that has already been set
error (line 1055)
Shows an error message and halts execution - use this in the same way as print_stop_message();
fetch_field (line 307)
Fetches info about the current data object - if a new value is set, it returns this, otherwise it will return the existing data
fetch_insert_sql (line 685)
Builds an INSERT/REPLACE query
fetch_update_sql (line 583)
Builds an UPDATE query
has_errors (line 839)
Check if the DM currently has errors. Will kill execution if it does and $die is true.
post_delete (line 1019)
Additional data to update after a delete call (such as denormalized values in other tables).
post_save_each (line 951)
Additional data to update after a save call (such as denormalized values in other tables).
In batch updates, is executed for each record updated.
post_save_once (line 965)
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.
pre_delete (line 1009)
Additional data to update before a delete call (such as denormalized values in other tables).
pre_save (line 931)
Any checks to run immediately before saving. If returning false, the save will not take place.
save (line 870)
Saves the data from the object into the specified database tables
set (line 339)
Sets the supplied data to be part of the data to be saved. Use setr() if a reference to $value is to be passed
setr (line 381)
Sets the supplied data to be part of the data to be saved
setr_info (line 459)
Rather like set(), but sets reference to data into the $this->info array instead
set_bitfield (line 423)
Sets a bit in a bitfield
set_condition (line 272)
Sets the condition to be used in WHERE clauses, based upon the $this->existing data and the $this->condition_constuct condition template.
set_error_handler (line 1034)
Sets the error handler for the object
set_existing (line 235)
Sets the existing data
set_failure_callback (line 1103)
Sets the function to call on an error.
set_info (line 444)
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
strip_empty_bbcode (line 1552)
Strips empty BB code from the entire message except inside PHP/HTML/Noparse tags.
strip_empty_bbcode_callback (line 1568)
Callback function for strip_empty_bbcode.
verify (line 480)
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.
verify_commalist (line 1274)
Verifies that a variable is a comma-separated list of integers
verify_date_array (line 1462)
Verifies a date array as a valid unix timestamp
verify_email (line 1419)
Verifies that an email address is valid
verify_image_count (line 1579)
Verifies the number of images in the post text. Call it from pre_save() after pagetext/allowsmilie has been set
verify_ipaddress (line 1377)
Verifies an IP address - currently only works with IPv4
verify_link (line 1432)
Verifies that a hyperlink is valid
verify_list (line 1300)
Creates a valid string of comma-separated integers
verify_md5 (line 1407)
Verifies that a string is an MD5 string
verify_nonempty (line 1260)
Verifies that a string is not empty
verify_nonzero (line 1235)
Verifies that an integer is greater than zero
verify_nonzero_or_negone (line 1248)
Verifies that an integer is greater than zero or the special value -1 this rule matches a fair number of id columns
verify_pagetext (line 1495)
Basic options to perform on all pagetext type fields
verify_serialized (line 1346)
Verifies that input is a serialized array (or force an array to serialize)
verify_spacelist (line 1286)
Verifies that a variable is a space-separated list of integers
verify_userid (line 1118)
Verifies that the specified user exists
verify_username (line 1144)
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