{{incomplete|needs technical review|Please check and see if this article is complete. If so, please remove the {{tl|incomplete}} from the beginning of the article.}}

Joomla provides a sophisticated database abstraction layer to simplify the usage for third party developers. New versions of the Joomla Platform API provide additional functionality which extends the database layer further, and includes features such as connectors to a greater variety of database servers and the query chaining to improve readability of connection code and simplify SQL coding.

Joomla provides a sophisticated database abstraction layer to simplify the usage for third party developers. New versions of the Joomla Platform API provide additional functionality which extends the database layer further, and includes features such as connectors to a greater variety of database servers and the query chaining to improve readability of connection code and simplify SQL coding.

Line 9:

Line 9:

===The Connection===

===The Connection===

−

Joomla supports a generic interface for connecting to the database, hiding the intricacies of a specific database server from the Framework developer, thus making Joomla code easier to port from one database to another.

+

Joomla supports a generic interface for connecting to the database, hiding the intricacies of a specific database server from the Framework developer, thus making Joomla code easier to port from one platform to another.

−

To obtain a database connection, use the JFactory getDbo static method:

+

To obtain a database connection, use the [http://api.joomla.org/Joomla-Platform/JFactory.html#getDbo JFactory getDbo] static method:

<source lang="php">

<source lang="php">

$db = JFactory::getDbo();

$db = JFactory::getDbo();

</source>

</source>

+

+

The getDbo method will return a reference to a high-level abstract class called [http://api.joomla.org/Joomla-Platform/Database/JDatabaseDriver.html JDatabaseDriver]; the Joomla Framework hides the specifics of the database server, which is loaded dynamically by getDbo via Joomla's configuration file.

{{JVer|3.0}} users should note that the JModel class has been renamed JModelLegacy and will eventually be deprecated in favour of the class JModelBase. Therefore, any Joomla 3.0 core or extension code should use JFactory::getDbo() to obtain a database connection.

+

{{JVer|3.1}} users should note that the JModel class has been renamed JModelLegacy and will eventually be deprecated in favour of the class JModelBase. Therefore, any Joomla 3.1 core or extension code should use JFactory::getDbo() to obtain a database connection.

===The Query===

===The Query===

Line 46:

Line 48:

====Selecting Records from a Single Table====

====Selecting Records from a Single Table====

+

+

Below is an example of creating a database query using the JDatabaseQuery class. Using the select, from, where and order methods, we can create queries which are flexible, easily readable and portable:

Chaining can become useful when queries become longer and more complex.

====Selecting Records from Multiple Tables====

====Selecting Records from Multiple Tables====

+

+

Using the JDatabaseQuery's [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#join join] methods, we can select records from multiple related tables. The generic "join" method takes two arguments; the join "type" (inner, outer, left, right) and the join condition. In the following example you will notice that we can use all of the keywords we would normally use if we were writing a native SQL query, including the AS keyword for aliasing tables and the ON keyword for creating relationships between tables. Also note that the table alias is used in all methods which reference table columns (I.e. select, where, order).

+

+

<source lang="php">

+

// Get a db connection.

+

$db = JFactory::getDbo();

+

+

// Create a new query object.

+

$query = $db->getQuery(true);

+

+

// Select all articles for users who have a username which starts with 'a'.

+

// Order it by the created date.

+

$query

+

->select(array('a.*', 'b.username', 'b.name'))

+

->from('#__content AS a')

+

->join('INNER', '#__users AS b ON (a.created_by = b.id)')

+

->where('b.username LIKE \'a%\'')

+

->order('a.created DESC');

+

+

// Reset the query using our newly populated query object.

+

$db->setQuery($query);

+

+

// Load the results as a list of stdClass objects.

+

$results = $db->loadObjectList();

+

</source>

+

+

The join method above enables us to query both the content and user tables, retrieving articles with their author details. There are also convenience methods for [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#innerJoin inner], [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#leftJoin left], [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#rightJoin right] and [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#outerJoin outer] joins.

+

+

We can use multiple joins to query across more than two tables:

+

+

<source lang="php">

+

$query

+

->select(array('a.*', 'b.username', 'b.name', 'c.*', 'd.*'))

+

->from('#__content AS a')

+

->join('INNER', '#__users AS b ON (a.created_by = b.id)')

+

->join('LEFT', '#__user_profiles AS c ON (b.id = c.user_id)')

+

->join('RIGHT', '#__categories AS d ON (a.catid = d.id)')

+

->where('b.username LIKE \'a%\'')

+

->order('a.created DESC');

+

</source>

+

+

Notice how chaining makes the source code much more readable for these longer queries.

====Inserting a Record====

====Inserting a Record====

+

+

=====Using SQL=====

+

+

The JDatabaseQuery class provides a number of methods for building insert queries, the most common being [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#insert insert], [http://api.joomla.org/11.4/Joomla-Platform/Database/JDatabaseQuery.html#columns columns] and [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#values values].

JError::$legacy is set to true in Joomla 2.5 in the CMS (if you are solely using the 11.4 platform this is set to false) and therefore a statement like this is needed. See [[Exceptions and Logging in Joomla 1.7 and Joomla Platform 11.1]]

+

+

Also note since Joomla 3.0 there has been a change in how the Joomla database class executes a query as well as the CMS setting JError::$legacy to false. Therefore everything now uses exceptions.

+

+

Since the phase out of PHP 4.x support, PHP's exception model has been widely implemented in the Joomla Framework. Therefore, we can wrap our database execution in a try...catch block to catch any unexpected database errors that may arise. Any database-specific errors will be thrown using an instance of the [http://api.joomla.org/Joomla-Platform/Database/JDatabaseException.html JDatabaseException] class although it is best practice to catch the generic Exception object from which JDatabaseException inherits.

+

+

=====Using an Object=====

+

+

The JDatabaseDriver also class provides us with a convenience method for saving an object directly to the database allowing us to add a record to a table without writing a single line of SQL.

Notice here that we do not need to escape the table name; the insertObject method does this for us.

+

+

The insertObject method will throw a [http://php.net/manual/en/class.runtimeexception.php RuntimeException] if there is a problem inserting the record into the database table.

+

+

We need to ensure that the record does not exist before attempting to insert it, so adding some kind of record check before executing the insertObject method would be recommended.

====Updating a Record====

====Updating a Record====

+

+

=====Using SQL=====

+

+

The JDatabaseQuery class also provides methods for building update queries, in particular [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#update update] and [http://api.joomla.org/Joomla-Platform/Database/JDatabaseQuery.html#set set]. We also reuse another method which we used when creating select statements, the where method.

Anything between the transactionStart and transactionCommit methods are not executed until transactionCommit is called. If an exception occurs, we can roll back the changes using the transactionRollback method. This allows us to return the database to the original state if a problem occurs even though we may execute a number of changes to the database's tables.

Joomla provides a sophisticated database abstraction layer to simplify the usage for third party developers. New versions of the Joomla Platform API provide additional functionality which extends the database layer further, and includes features such as connectors to a greater variety of database servers and the query chaining to improve readability of connection code and simplify SQL coding.

Usage

Joomla can use different kinds of SQL database systems and run in a variety of environments with different table-prefixes. In addition to these functions, the class automatically creates the database connection. Besides instantiating the object you need just two lines of code to get a result from the database in a variety of formats. Using the Joomla database layer ensures a maximum of compatibility and flexibility for your extension.

The Connection

Joomla supports a generic interface for connecting to the database, hiding the intricacies of a specific database server from the Framework developer, thus making Joomla code easier to port from one platform to another.

The getDbo method will return a reference to a high-level abstract class called JDatabaseDriver; the Joomla Framework hides the specifics of the database server, which is loaded dynamically by getDbo via Joomla's configuration file.

users should note that the JModel class has been renamed JModelLegacy and will eventually be deprecated in favour of the class JModelBase. Therefore, any Joomla 3.1 core or extension code should use JFactory::getDbo() to obtain a database connection.

The Query

Joomla's database querying has changed since the new Joomla Framework was introduced "query chaining" is now the recommended method for building database queries (although string queries are still supported).

Query chaining refers to a method of connecting a number of methods, one after the other, with each method returning an object that can support the next method, improving readability and simplifying code.

To obtain a new instance of the JDatabaseQuery class we use the JDatabaseDriver getQuery method:

$db= JFactory::getDbo();$query=$db->getQuery(true);

The JDatabaseDriver::getQuery takes an optional argument, $new, which can be true or false (the default being false).

To query our data source we can call a number of JDatabaseQuery methods; these methods encapsulate the data source's query language (in most cases SQL), hiding query-specific syntax from the developer and increasing the portability of the developer's source code.

Some of the more frequently used methods include; select, from, join, where and order. There are also methods such as insert, update and delete for modifying records in the data store. By chaining these and other method calls, you can create almost any query against your data store without compromising portability of your code.

Selecting Records from a Single Table

Below is an example of creating a database query using the JDatabaseQuery class. Using the select, from, where and order methods, we can create queries which are flexible, easily readable and portable:

// Get a db connection.$db= JFactory::getDbo();// Create a new query object.$query=$db->getQuery(true);// Select all records from the user profile table where key begins with "custom.".// Order it by the ordering field.$query->select(array('user_id','profile_key','profile_value','ordering'));$query->from('#__user_profiles');$query->where('profile_key LIKE \'custom.%\'');$query->order('ordering ASC');// Reset the query using our newly populated query object.$db->setQuery($query);// Load the results as a list of stdClass objects.$results=$db->loadObjectList();

Chaining can become useful when queries become longer and more complex.

Selecting Records from Multiple Tables

Using the JDatabaseQuery's join methods, we can select records from multiple related tables. The generic "join" method takes two arguments; the join "type" (inner, outer, left, right) and the join condition. In the following example you will notice that we can use all of the keywords we would normally use if we were writing a native SQL query, including the AS keyword for aliasing tables and the ON keyword for creating relationships between tables. Also note that the table alias is used in all methods which reference table columns (I.e. select, where, order).

// Get a db connection.$db= JFactory::getDbo();// Create a new query object.$query=$db->getQuery(true);// Select all articles for users who have a username which starts with 'a'.// Order it by the created date.$query->select(array('a.*','b.username','b.name'))->from('#__content AS a')->join('INNER','#__users AS b ON (a.created_by = b.id)')->where('b.username LIKE \'a%\'')->order('a.created DESC');// Reset the query using our newly populated query object.$db->setQuery($query);// Load the results as a list of stdClass objects.$results=$db->loadObjectList();

The join method above enables us to query both the content and user tables, retrieving articles with their author details. There are also convenience methods for inner, left, right and outer joins.

We can use multiple joins to query across more than two tables:

$query->select(array('a.*','b.username','b.name','c.*','d.*'))->from('#__content AS a')->join('INNER','#__users AS b ON (a.created_by = b.id)')->join('LEFT','#__user_profiles AS c ON (b.id = c.user_id)')->join('RIGHT','#__categories AS d ON (a.catid = d.id)')->where('b.username LIKE \'a%\'')->order('a.created DESC');

Notice how chaining makes the source code much more readable for these longer queries.

Inserting a Record

Using SQL

The JDatabaseQuery class provides a number of methods for building insert queries, the most common being insert, columns and values.

// Get a db connection.$db= JFactory::getDbo();// Create a new query object.$query=$db->getQuery(true);// Insert columns.$columns=array('user_id','profile_key','profile_value','ordering');// Insert values.$values=array(1001,$db->quote('custom.message'),$db->quote('Inserting a record using insert()'),1);// Prepare the insert query.$query->insert($db->quoteName('#__user_profiles'))->columns($db->quoteName($columns))->values(implode(',',$values));// Reset the query using our newly populated query object.$db->setQuery($query);

When executing a query in the Joomla Framework 11.4 we use the JDatabase's query method:

Also note since Joomla 3.0 there has been a change in how the Joomla database class executes a query as well as the CMS setting JError::$legacy to false. Therefore everything now uses exceptions.

Since the phase out of PHP 4.x support, PHP's exception model has been widely implemented in the Joomla Framework. Therefore, we can wrap our database execution in a try...catch block to catch any unexpected database errors that may arise. Any database-specific errors will be thrown using an instance of the JDatabaseException class although it is best practice to catch the generic Exception object from which JDatabaseException inherits.

Using an Object

The JDatabaseDriver also class provides us with a convenience method for saving an object directly to the database allowing us to add a record to a table without writing a single line of SQL.

// Create and populate an object.$profile=new stdClass();$profile->user_id=1001;$profile->profile_key='custom.message';$profile->profile_value='Inserting a record using insertObject()';$profile->ordering=1;
try {// Insert the object into the user profile table.$result= JFactory::getDbo()->insertObject('#__user_profiles',$profile);} catch (Exception $e){// catch any errors.}

Notice here that we do not need to escape the table name; the insertObject method does this for us.

The insertObject method will throw a RuntimeException if there is a problem inserting the record into the database table.

We need to ensure that the record does not exist before attempting to insert it, so adding some kind of record check before executing the insertObject method would be recommended.

Updating a Record

Using SQL

The JDatabaseQuery class also provides methods for building update queries, in particular update and set. We also reuse another method which we used when creating select statements, the where method.

$db= JFactory::getDbo();$query=$db->getQuery(true);// Fields to update.$fields=array('profile_value=\'Updating custom message for user 1001.\'','ordering=2');// Conditions for which records should be updated.$conditions=array('user_id=42','profile_key=\'custom.message\'');$query->update($db->quoteName('#__user_profiles'))->set($fields)->where($conditions);$db->setQuery($query);
try {$result=$db->query();// Use $db->execute() for Joomla 3.0.} catch (Exception $e){// Catch the error.}

Using an Object

Like insertObject, the JDatabaseDriver class provides a convenience method for updating an object.

Below we will update our custom table with new values using an existing id primary key:

// Create an object for the record we are going to update.$object=new stdClass();// Must be a valid primary key value.$object->id=1;$object->title='My Custom Record';$object->description='A custom record being updated in the database.';
try {// Update their details in the users table using id as the primary key.$result= JFactory::getDbo()->updateObject('#__custom_table',$object,'id');} catch (Exception $e){// catch the error.}

Just like insertObject, updateObject takes care of escaping table names for us.

The updateObject method will throw a RuntimeException if there is a problem inserting the record into the database table.

We need to ensure that the record already exists before attempting to update it, so we would probably add some kind of record check before executing the updateObject method.

Deleting a Record

Just as there are select, insert and update method calls, there is also a delete method for remove records from the database.

Anything between the transactionStart and transactionCommit methods are not executed until transactionCommit is called. If an exception occurs, we can roll back the changes using the transactionRollback method. This allows us to return the database to the original state if a problem occurs even though we may execute a number of changes to the database's tables.