1. Developing a Model-View-Controller Component for Joomla Part 3
Using a Database

2. Introduction
In the first two tutorials, we showed you how to build a simple model-view-controller component. We had one view which retrieved data from a model (which was created in the 2nd tutorial). In this tutorial, we will be working with the model. Instead of the data being hard coded in the model, the model will retrieve the data from a table in the database.
This tutorial will demonstrate how to use the JDatabase class to retrieve data from the database.

3. Retrieving the Data
Our model currently has one method: getGreeting(). This method is very simple - all it does is return the hard-coded greeting.
To make things more interesting, we will load the greeting from a database table. We will demonstrate later how to create an SQL file and add the appropriate code to the XML manifest file so that the table and some sample data will be created when the component is installed. For now, we will simply replace our return statement with some code that will retrieve the greeting from the database and return it.
The first step is to obtain a reference to a database object. Since Joomla! uses the database for its normal operation, a database connection already exists; therefore, it is not necessary to create your own. A reference to the existing database can be obtained using:
$db =& JFactory::getDBO();

4. Retrieving the Data
JFactory is a static class that is used to retrieve references to many of the system objects.
The method name (getDBO) stands for get DataBase Object, and is easy and important to remember.
Now that we have obtained a reference to the database object, we can retrieve our data. We do this in two steps:
store our query in the database object
load the result

5. Retrieving the Data
Our new getGreeting() method will therefore look like:
hello is the name of the table that we will create later, and greeting is the name of the field that stores the greetings. If you are not familiar with SQL, it would be helpful to take a tutorial or a lesson to get yourself up to speed. There are many such tutorials on the web and they are easily found using search engines.
The $db->loadResult() method will execute the stored database query and return the first field of the first row of the result.

6. Creating the Installation SQL File
The Joomla! installer has built-in support for executing queries during component installation. These queries are all stored in a standard text file.
We will have three queries in our install file: the first will drop the table in case it already exists, the second will create the table with the appropriate fields, and the third will insert the data.
Here are our queries:

7. Creating the Installation SQL File
You might find the prefix on the table names rather odd. Joomla! will replace this prefix with the prefix used by the current install. For most installs, this table will become jos_hello. This allows multiple installs of Joomla! to use the same database, and prevents collisions with other applications using the same table names (i.e. two applications might share a database, but might both require a 'users' table. This convention avoids problems.)
We have specified two fields in our database. The first field is id, and is called the 'primary key'. The primary key of a database table is a field that is used to uniquely identify a record. This is often used to lookup rows in the database. The other field is greeting. This is the field that stores the greeting that is returned from the query that we used above.
We will save our installation queries in a file called admin/install.sql.

8. Creating the Uninstall SQL File
Though we might hope that people will never want to "uninstall" our component, it is important that if they do, nothing is left behind after uninstalling our component. Joomla! will look after deleting the files and directories that were created during the "install", but we must manually include queries that will remove any tables that were added to the database. Since we have only created one table, we only need one query:
DROP TABLE IF EXISTS `#__hello`;
We will save this uninstall query in a file called admin/uninstall.sql

9. Updating our XML File
We need to change a few things in our hello.xml file. First, we need to add our two new sql files to the list of files to install. Secondly, the SQL install files have to be placed in the admin directory. Thirdly, we need to tell the installer to execute the queries in our files on install and uninstall.

10. Updating our XML File