Latest releases

DB_Table 1.5.2

2008-05-14T14:38:43-05:00

- Bug #13701: Undefined variable $db in Generator.php
(thanks to Youichi Okada)
- Bug #13728: generator produced invalid variable names (e.g. containing a dot)
(thanks to Peter Pawluczuk)

DB_Table 1.5.1

2008-03-28T15:20:56-05:00

- this package is now licensed under the New BSD license
- Request #12136: support for 'qf_type' == 'link' is now available, providing
access to the "link" element of HTML_QuickForm; the link href needs to be
specified in the 'qf_href' key, the link text needs to be specified in the
'qf_setvalue' key
(thanks to Diederick Huijbers)
- Bug #12190: missing error return in DB_Table_Manager::create()
(thanks to Carsten Wiedmann for the patch)
- Bug #12208: wrong verification of clob fields with mysql(i) backend
(thanks to Carsten Wiedmann)
- Bug #12247: 'require' attribute is name 'required' in Generator
(thanks to Gregor Gramlich)
- Bug #12497: Generator works only with DB, but not with MDB2
(thanks to Carsten Wiedmann for the patch)
- Request #12510: various optimizations (mostly coding standards) and
corrections (missing error return call, change MDB2's portability mode only
temporarily)
(thanks to Carsten Wiedmann for the patch)
- Request #13267: constructor's $table parameter is now optional; this change
allows to set a fixed table name via the $table property in the DB_Table
subclass

DB_Table 1.5.0

2007-06-27T18:27:30-05:00

This is the first stable release that contains some signficant enhancements to DB_Table. The main changes since release 1.4.0 are:
- A new DB_Table_Database class, which contains a model of relationships between tables. The class contains methods to simplify the construction of joins, check foreign key validity, and emulate referentially triggered ON DELETE and ON UPDATE actions.
- A new DB_Table_Generator class, which generates PHP code necessary for an existing database. Generates a skeleton DB_Table subclass definition for each table in the database.
- A new DB_Table_Base class, as an abstract parent class for DB_Table and DB_Table_Database.
- Added auto-increment column declarations to DB_Table
- Select*() methods can now process query arrays passed as arguments (as well as stored queries).
- XML support, using the MDB2 XML schema. XML Serialization and unserialization of the database model.
- Full unit tests for DB_Table_Database.
- Full documentation added to the PEAR manual.

The only changes since release 1.5.0RC3 are changes to the organization of the DB_Table_Database unit tests, and inclusion of a simple form of regression testing. See tests/database/README.

DB_Table 1.5.0RC3

2007-06-14T15:12:03-05:00

- Added complete documentation in the PEAR manual.
- new DB_Table_Base class added. This is a parent class for DB_Table and DB_Table_Database that contains methods and properties common to both classes.
- The DB_Table::select*() and DB_Table::buildSQL() methods, which are now inherited from the DB_Table_Base class, now accept either a query array or (as before) a key of the $sql property array as a first argument.
- Added DB_Table_Database::onDeleteAction() and DB_Table_Database::onUpdateAction() methods, which implement referentially triggered actions (e.g., cascading deletes). This code had previously been part of the DB_Table_Database insert() and update() methods.
- Changed behavior of DB_Table::insert() and DB_Table::update() method for a DB_Table object that is part of a DB_Table_Database instance: If a parent DB_Table_Database object exists, these methods can now validate foreign keys and implement ON DELETE and ON UPDATE actions, if these behaviors are enabled in the parent DB_Table_Database object. The behaviors of the DB_Table and DB_Table_Database insert and update methods are now identical. (This is a BC break with 1.5.0RC1 and 1.5.0RC2 beta releases, but not with earlier stable releases.)
- Disable automatic foreign key validation by default (BC break with releases 1.5.0RC1 and 1.5.0RC2).
- Added buildFilter() method to the DB_Table_Base class. This a simplified version of the DB_Table_Database::buildFilter() method of previous 1.5.0RC* releases. (BC break with 1.5.0RC1 and 1.5.0RC2)
- Added a private DB_Table_Database::_buildForeignKeyFilter() for more specialized uses of the old buildFilter() method, which are used internally to construct queries.
- Changed return value of DB_Table_Database::validForeignKey on failure from boolean false to PEAR_Error. Changed related error codes.
- Changed element of XML output to for consistency with MDB2 XML schema.
- Simplified unit tests for DB_Table_Database by adding a parent DatabaseTest unit test class.

DB_Table 1.5.0RC2

2007-03-24T23:37:20-05:00

- new DB_Table_Generator class added. This class generates code required as an interface to an existing database by reverse engineering the databcase. It generates a DB_Table subclass definition for each table, and a script that instantiates one instance of each DB_Table subclass, and a parent DB_Table_Database object. See the documentation block for the new class for usage instructions, and the tests/generator/tests.php script for an example.

DB_Table 1.5.0RC1

2007-02-06T01:32:31-05:00

- New DB_Table_Database class added to package. The new class provides a model
of foreign key relationships between tables in a database, and features that
depend on knowledge of these relationships. User documentation for this
class is provided in docs/database/manual.html.
- Added auto-increment feature to DB_Table insert() method. The value of a new
$auto_inc_col property is the name of an auto-increment column (if any) or
null.
- added toXML() method to DB_Table, which emits the table schema in the MDB2
XML DTD, with an extension to describe foreign key references. This method
is called by the toXML() method of DB_Table_Database, which emits an XML
schema string for an entire database.

DB_Table 1.4.0

2006-11-09T15:57:28-05:00

- Static form elements like 'header', 'static', 'submit' or 'reset' can now
easily be added: define an array called $frm in your class, create a form
object (e.g. yourself, via $obj->getForm(), ...) and then call
$obj->addStaticFormElements($form);
The $frm array has a very similar format like the column definition format. The
key is the field name and the value is an array with details about the element.
There is a special key called 'before' in the details array. If it is not
given, or is empty (or null) the element will be appended at the end. If it is
given, the element is added before the element specified via 'before'.
Example:
var $frm = array('headline' => array('before' => 'name',
'qf_type' => 'header',
'qf_setvalue' => 'Headline'
),
'submit' => array('before' => null,
'qf_type' => 'submit',
'qf_setvalue' => 'Save data'
));
This example assumes that there is an element called 'name' in the form. The
header element will be placed before this 'name' element, and the submit button
will be placed at the end of the form.
- added support for 'hierselect' and 'jscalendar' QuickForm elements as
'qf_type' values in the column definition arrays
(thanks to Arne Bippes and QDog for the patches)
- fixes / optimizations for columns with 'qf_type' == 'file':
* if the column is marked as required, the 'uploadedfile' QF rule is now set
instead of the 'required' QF rule
* the 'numeric' and 'maxlength' QF rules are not set anymore (the corresponding
checks will still be done before inserting/updating data into the database)
- fixed wrong handling of errors in the constructor

DB_Table 1.3.2

2006-07-25T06:25:46-05:00

- Bug #8249: occured wrongly between grouped radio buttons
(thanks to Arne Bippes, arne dot bippes at brandao dot de)
- Renamed the key 'qf_radiosep' for the separator of grouped QuickForm elements
into 'qf_groupsep', as it is not only used for radio buttons

DB_Table 1.3.1

2006-07-19T05:33:43-05:00

- updated the allowed data types for 'alter' and 'verify' modes according to
the latest MDB2 changes

DB_Table 1.3.0

2006-04-26T11:56:35-05:00

Short summary:
* New table creation modes 'verify' and 'alter'
* Primary keys are now supported
* MDB2 is now supported as database backend
* Firebird DBMS is now supported (but Interbase isn't)
* Auto-creation of QuickForm rules can be disabled now
* Usage of QuickForm and custom QuickForm elements is now more flexible
* Internationalizing/customizing of error messages now easier

Minor changes in detail:
* Improvement related to bug report #5679: many arrays (in the
table definition and as function parameters) may now be null
(of course, an empty array is still allowed).
* The column definition array $col may not be empty because it
isn't possible to create empty database tables and because
the work with DB_Table makes only sense with at least one
column.
* Fixed several return by reference problems (that caused
notices in PHP 4.4.x and 5.x).
* Fixed several "undefined index" problems (causing notices).
* Bugfix: select() and selectResult() didn't return error
objects caused due to problems in $sql array.
* Bugfix: static usage of DB_Table_QuickForm::createForm()
resulted in fatal error when 'formName' wasn't specified
in the $args parameter.
* Request #5965: Turn off automatic setting of default QF rules
like 'numeric' or 'required' (can be done by setting
$cols[...]['qf_set_default_rules'] = false).
(thanks to Arne Bippes)
* Bug #6025: DB_Table no longer tries to create a table if a
table with the same name but with different use of lower and
upper letters.
* Request #6036: new qf_type 'callback' which allows to add
custom QF elements that need more than the standard
parameters. You need to specify a key named 'qf_callback',
filled with either the name of a class (this class needs to
have a method 'createElement') or the name of a method.
Both method types must return true if the element was created
successfully. (thanks to Arne Bippes)
* The dependency on the Date package was removed.
* In addition to the option to internationalize some error messages
via $GLOBALS['_DB_TABLE']['error'], you can now use
setErrorMessage() like this (assuming $obj is your DB_Table instance):
$obj->setErrorMessage(DB_TABLE_ERR_PHPTYPE, 'localized message');
or to set more than one message:
$obj->setErrorMessage(array(DB_TABLE_ERR_PHPTYPE => 'message 1',
DB_TABLE_ERR_NOT_DB_OBJECT => 'message 2'));
Static calls (DB_Table::setErrorMessage(...)) are also valid.
Setting the error messages via a static call or $GLOBALS is
especially needed for errors that can occur with-in the
constructor call (i.e. e.g. creating or altering the database table).
* Fixed handling of QuickForm rules: If there was a server-side-only
rule (like 'uploadedfile'), client-side validation was disabled
for all rules. Now it is disabled only for server-side-only rules.
* You can now use an extended HTML_QuickForm object by specifying
the class name in $_DB_TABLE['qf_class_name']. (Attention: You
have to include the extended class file yourself.)

Major changes / enhancements in detail:
* Request #5478: Verification/check, whether the table exists,
whether all the columns exist, whether the columns have the
right type, and whether the indexes exists. This can be used
by setting $create in the constructor of your extended class
to 'verify' instead of false/'safe'/'drop'. In case of an
error in the schema, you will find the PEAR_Error object in
$obj->error (assuming $obj is your DB_Table instance).
- This is not available for 'fbsql' and 'mssql' phptypes.
('fbsql' is likely to be not supported in the future, while
'mssql' will be added when MDB2 has support for index and
constraint information for this DBMS.)
* New creation mode 'alter': If the table does not exist, it will
be created. Otherwise, table fields' existance and types will be
checked and, if needed, the field(s) will be added or changed. The
same applies for indexes' and constraints' existance and types.
Columns/indexes/constraints that don't exist anymore in the table
definition class, will NOT be removed.
- This is a new and powerful feature, use it with caution -- changing
a string datatype into a numeric datatype in your table definition
class may lead to data loss.
- Using " $_DB_TABLE['debug'] = true; " in your scripts will
output what will be changed. If something unexpected is changed,
please report it via PEAR's bug tracker (please include the
debug message and the column and/or index definition from your
table definition class, thanks).
- This is not available for 'fbsql' and 'mssql' phptypes.
('fbsql' is likely to be not supported in the future, while
'mssql' will be added when MDB2 has support for index and
constraint information for this DBMS.)
(thanks to Arne Bippes for the initial idea)
* Support for primary keys: In the $idx array one index can be
marked as 'primary' and will be created as the primary key of
the chosen table.
- This not available for 'sqlite' phptype, as SQLite does not
support primary keys.
* Request #6384: DB_Table now supports also MDB2 as the database
backend. Just pass an MDB2 instance instead of a DB instance to
the constructor. (thanks to Lukas Smith for the initial patch)
* DB_Table now supports the Firebird DBMS (version >= 1.5
required). Because of the limited features of Interbase
(its ancestor), only Firebird is supported. Therefore,
'dbsyntax' must be set to 'firebird' in your DSN. Please note
that the ibase extension is very buggy in PHP 4, while it works
good with PHP 5.

Only relevant if you are using localized error messages:
* Please note that there are eleven new error messages and that the
messages for DB_TABLE_ERR_NOT_DB_OBJECT and DB_TABLE_ERR_PHPTYPE
slightly differ from the old messages.