Class: MDB2_Tools_Manager
Source Location: /MDB2-2.0.0beta3/MDB2/Tools/Manager.php
PEAR
|
--MDB2_Tools_Manager
The database manager is a class that provides a set of database management services like installing, altering and dumping the data structures of databases.
Author(s):
|
|
|
Inherited Variables
|
Inherited Methods
|
Class Details
Class Variables
Method Detail
alterDatabase [line 1519]
mixed alterDatabase(
array
$changes, [array
$current_definition = null])
|
|
Execute the necessary actions to implement the requested changes in a database structure.
Parameters:
alterDatabaseIndexes [line 1382]
mixed alterDatabaseIndexes(
string
$table_name, array
$changes, array
$current_definition)
|
|
Execute the necessary actions to implement the requested changes in the indexes inside a database structure.
Parameters:
alterDatabaseSequences [line 1472]
mixed alterDatabaseSequences(
array
$changes, array
$current_definition)
|
|
Execute the necessary actions to implement the requested changes in the sequences inside a database structure.
Parameters:
alterDatabaseTables [line 1423]
mixed alterDatabaseTables(
array
$changes, array
$current_definition)
|
|
Execute the necessary actions to implement the requested changes in the tables inside a database structure.
Parameters:
compareDefinitions [line 862]
mixed compareDefinitions(
array
$previous_definition, [array
$current_definition = null])
|
|
compare a previous definition with the currenlty parsed definition
Parameters:
compareSequenceDefinitions [line 1249]
mixed compareSequenceDefinitions(
array
$sequence_name, array
$previous_definition,
$current_definition,
&$defined_sequences)
|
|
compare a previous definition with the currenlty parsed definition
Parameters:
compareTableDefinitions [line 1167]
mixed compareTableDefinitions(
string
$table_name, array
$previous_definition, array
$current_definition,
&$defined_tables)
|
|
compare a previous definition with the currenlty parsed definition
Parameters:
compareTableFieldsDefinitions [line 929]
mixed compareTableFieldsDefinitions(
string
$table_name, array
$previous_definition, array
$current_definition,
&$defined_fields)
|
|
compare a previous definition with the currenlty parsed definition
Parameters:
compareTableIndexesDefinitions [line 1071]
mixed compareTableIndexesDefinitions(
string
$table_name, array
$previous_definition, array
$current_definition,
&$defined_indexes)
|
|
compare a previous definition with the currenlty parsed definition
Parameters:
connect [line 245]
mixed connect(
&$dbinfo, [mixed
$options = false], mixed
$dbinfo)
|
|
Create a new MDB2 connection object and connect to the specified database
Parameters:
createDatabase [line 746]
Create a database space within which may be created database objects like tables, indexes and sequences. The implementation of this function is highly DBMS specific and may require special permissions to run successfully. Consult the documentation or the DBMS drivers that you use to be aware of eventual configuration requirements.
createTable [line 539]
mixed createTable(
string
$table_name, array
$table, [boolean
$overwrite = false])
|
|
create a table and inititialize the table if data is available
Parameters:
createTableIndexes [line 492]
mixed createTableIndexes(
string
$table_name, array
$indexes, boolean
$overwrite)
|
|
create a indexes om a table
Parameters:
debugOutput [line 148]
disconnect [line 273]
Log out and disconnect from the database.
dropSequence [line 719]
mixed dropSequence(
string
$sequence_name)
|
|
drop a table
Parameters:
dropTable [line 635]
mixed dropTable(
string
$table_name)
|
|
drop a table
Parameters:
dumpDatabase [line 1745]
mixed dumpDatabase(
array
$arguments, [integer
$dump = MDB2_MANAGER_DUMP_ALL])
|
|
Dump a previously parsed database structure in the Metabase schema XML based format suitable for the Metabase parser. This function may optionally dump the database definition with initialization commands that specify the data that is currently present in the tables.
Parameters:
dumpDatabaseChanges [line 1588]
mixed dumpDatabaseChanges(
array
$changes)
|
|
Dump the changes between two database definitions.
Parameters:
getDefinitionFromDatabase [line 340]
mixed getDefinitionFromDatabase(
)
|
|
Attempt to reverse engineer a schema structure from an existing MDB2 This method can be used if no xml schema file exists yet. The resulting xml schema file may need some manual adjustments.
getOption [line 217]
mixed getOption(
string
$option)
|
|
returns the value of an option
Parameters:
getWarnings [line 177]
get all warnings in reverse order. This means that the last warning is the first element in the array
initializeTable [line 592]
mixed initializeTable(
string
$table_name, array
$table)
|
|
inititialize the table with data
Parameters:
parseDatabaseDefinitionFile [line 312]
mixed parseDatabaseDefinitionFile(
string
$input_file, array
$variables, [bool
$fail_on_invalid_names = true])
|
|
Parse a database definition file by creating a Metabase schema format parser object and passing the file contents as parser input data stream.
Parameters:
raiseError [line 134]
object a &raiseError(
[mixed
$code = null], [int
$mode = null], [mixed
$options = null], [string
$userinfo = null], mixed
$nativecode)
|
|
This method is used to communicate an error and invoke error callbacks etc. Basically a wrapper for PEAR::raiseError without the message string.
Parameters:
resetWarnings [line 161]
setDatabase [line 291]
string setDatabase(
string
$name)
|
|
Select a different database
Parameters:
setOption [line 193]
mixed setOption(
string
$option, mixed
$value)
|
|
set the option for the db class
Parameters:
updateDatabase [line 1826]
mixed updateDatabase(
string
$current_schema_file, [string
$previous_schema_file = false], [array
$variables = array()])
|
|
Compare the correspondent files of two versions of a database schema definition: the previously installed and the one that defines the schema that is meant to update the database. If the specified previous definition file does not exist, this function will create the database from the definition specified in the current schema file. If both files exist, the function assumes that the database was previously installed based on the previous schema file and will update it by just applying the changes. If this function succeeds, the contents of the current schema file are copied to replace the previous schema file contents. Any subsequent schema changes should only be done on the file specified by the $current_schema_file to let this function make a consistent evaluation of the exact changes that need to be applied.
Parameters:
verifyAlterDatabase [line 1317]
mixed verifyAlterDatabase(
array
$changes)
|
|
verify that the changes requested are supported
Parameters:
Documentation generated on Mon, 11 Mar 2019 14:28:17 -0400 by phpDocumentor 1.4.4. PEAR Logo Copyright © PHP Group 2004.
|
|