J2.5:Accessing the database using JDatabase - Revision history

Wilsonge: Redirected page to Accessing the database using JDatabase

2013-09-01T21:54:26Z

Redirected page to Accessing the database using JDatabase

Wilsonge: Wilsonge moved page Accessing the database using JDatabase/2.5 to J2.5:Accessing the database using JDatabase: Move to 2.5 namespace

2013-06-06T10:03:31Z

Wilsonge moved page Accessing the database using JDatabase/2.5 to J2.5:Accessing the database using JDatabase: Move to 2.5 namespace

← Older revision	Revision as of 10:03, 6 June 2013
(No difference)

Wilsonge: Update 3.0 to 3.1

2013-04-29T09:55:22Z

Update 3.0 to 3.1

← Older revision		Revision as of 09:55, 29 April 2013
Line 25:		Line 25:
	</source>		</source>

	{{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.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===

Wilsonge: Update 3.0 to 3.1

2013-04-29T09:55:08Z

Update 3.0 to 3.1

← Older revision		Revision as of 09:55, 29 April 2013
Line 25:		Line 25:
	</source>		</source>

	{{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.0 core or extension code should use JFactory::getDbo() to obtain a database connection.

	===The Query===		===The Query===

Wilsonge: /* Using SQL */

2013-02-09T12:32:57Z

Using SQL

← Older revision		Revision as of 12:32, 9 February 2013
Line 156:		Line 156:
	$db->setQuery($query);		$db->setQuery($query);
	</source>		</source>

	~~Since Joomla 3.0 there has been a change in how the Joomla database class executes a query.~~

	When executing a query in the Joomla Framework 11.4 we use the JDatabase's [http://api.joomla.org/11.4/Joomla-Platform/Database/JDatabase.html#query query] method:		When executing a query in the Joomla Framework 11.4 we use the JDatabase's [http://api.joomla.org/11.4/Joomla-Platform/Database/JDatabase.html#query query] method:
Line 185:		Line 183:

	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]]		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.		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.

Wilsonge: /* Using SQL */

2013-02-09T12:32:02Z

Using SQL

← Older revision		Revision as of 12:32, 9 February 2013
Line 170:		Line 170:
	</source>		</source>

	~~For~~ Joomla ~~Framework 12~~.~~1 and higher, we use~~ the ~~JDatabaseDriver~~'~~s [http://api~~.~~joomla.org/Joomla-Platform/Database/JDatabaseDriver.html#execute execute] method~~:		Note that whilst the Joomla 2.5 platform has php exceptions support the Joomla 2.5 CMS system '''doesn't'''. Therefore when executing queries it is better practice to do something along the lines of:

	<source lang="php">		<source lang="php">
	~~try {~~		// Legacy error handling switch based on the JError::$legacy switch.
	// ~~Execute~~ the ~~query in Joomla 3~~.0.		// @deprecated 11.3
	$~~result = $db->execute~~();		if (JError::$legacy) {
	~~} catch~~ (~~Exception~~ $e) {		JError::setErrorHandling(E_ERROR, 'die');
	~~// catch any database errors.~~		return JError::raiseError(500, JText::sprintf('JLIB_DATABASE_ERROR_LOAD_DATABASE_DRIVER', $options['driver']));
			}
			else {
			throw new DatabaseException(JText::sprintf('JLIB_DATABASE_ERROR_LOAD_DATABASE_DRIVER', $options['driver']));
	}		}
	</source>		</source>

			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]]

	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.		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.

Dfritsch: /* Using SQL */

2013-02-09T09:02:30Z

Using SQL

← Older revision		Revision as of 09:02, 9 February 2013
Line 236:		Line 236:
	try {		try {
	$result = $db->query(); // Use $db->execute() for Joomla 3.0.		$result = $db->query(); // Use $db->execute() for Joomla 3.0.
	catch (Exception $e) {		} catch (Exception $e) {
	// Catch the error.		// Catch the error.
	}		}

Dfritsch: /* Using an Object */

2013-02-09T09:02:05Z

Using an Object

← Older revision		Revision as of 09:02, 9 February 2013
Line 198:		Line 198:
	// Insert the object into the user profile table.		// Insert the object into the user profile table.
	$result = JFactory::getDbo()->insertObject('#__user_profiles', $profile);		$result = JFactory::getDbo()->insertObject('#__user_profiles', $profile);
	catch (Exception $e) {		} catch (Exception $e) {
	// catch any errors.		// catch any errors.
	}		}

Wilsonge at 21:24, 4 February 2013

2013-02-04T21:24:21Z

← Older revision		Revision as of 21:24, 4 February 2013
Line 1:		Line 1:
	{{~~underconstruction~~}}		{{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.

Haydenyoung at 17:08, 20 November 2012

2012-11-20T17:08:08Z

← Older revision		Revision as of 17:08, 20 November 2012
Line 1:		Line 1:
	{{~~inuse~~}}		{{underconstruction}}

	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.