We have code in place that connects to the database and runs a query against it.

It's now time to work with the results.

We have those results in a variable named results.

However, that variable is not a simple array like you might think.

It's actually a new kind of php object.

Let's take a look at the documentation.

>> Let's go back to workspaces and the connection.php file.

We connect to the database and if that successful, we run our query.

If that query is successful,

then we have the return value of the query method in a variable named results.

Let's look in more detail at this results variable.

Let's remove this temporary success message.

And then we'll jump down below our try catch block.

We only need to put the code that actually interacts with the database

in that try catch block.

Let's display information about this results variable to the screen with

the var_dump.

Now let's go back in the browser.

You can see that the variable is an object.

It's a different kind of object than what we've seen so far.

It's not an object of the php mailer class, nor an object of the pdo class.

It's a pdo statement object.

Remember, that an object is a collection of variables, called properties, and

functions, called methods.

All bundled together when you display information about an object to the screen

like this you'll see its list of properties.

This object has one property query string.

It contains a query string we just ran.

But how would we find which methods this object has?

The pdo statement is a native class in php.

So we can find details in the php manual.

Lets perform a search for pdo statement.

[NOISE] The first result is a link to the php manual.

Looking at the instructions, you can see that this object represents a prepared

statement, and after that statement is executed and associated, result set.

We'll talk more about prepared statements a little later.

Right now, let's look at the result set.

Here's a list of methods.

These methods are available for all objects of this class.

Some of these have names that might look obscure.

Like bindParam.

But will look more in-depth into the methods will be using in this project.

Scrolling down past this list of methods.

You can see all the method names here with a little bit of a description.

Let's see.

This fetch all method looks promising.

It returns an array containing all the result set rows.

In other words it organizes the data the database returns into an array.

Let's go back to our code.

We'll call the fetch all method without any arguments.

Now let's go back in the browser and take a look at these results.

The array has 36 elements, one for each item in the database.

If we view the page source, we can see this a little more clearly.

Each of our 36 elements then has an internal array

with each of the attributes of that item.

We've now written code that uses php data objects to query the database and

to load the results in a php array.

Although this array does resemble our catalog array in the next video

we'll be fine tuning these results to allow us to swap them out for

our current catalog array.