# Using Illuminate Database With Eloquent in Your PHP App Without Laravel

Illuminate is Laravel’s database engine minus Laravel. It comes bundled with the Eloquent ORM in Laravel. If you would like to build your PHP apps with ORMs and prefer not to use Laravel, this tutorial is for you.

In this tutorial, we are going to build the back end for a Q&A App with PHP, Illuminate Database, and the Eloquent ORM.

1. PHP: 5.5+
2. MYSQL
3. Composer

## App Capabilities

Our app will perform ten tasks:

• Get a question with answers.
• Get all questions and users who asked them.
• Count questions by a particular user.
• Delete a question.

First, we create our project directory and structure.

In the main project directory, we’ll create an app folder, and then in this app folder, we’ll create two folders: models and controllers. In this picture, our main project folder is named eloquent. You should replace it with whatever name you prefer.

Next, we create an index.php file in the main project folder, at the same level as the app folder.

We will use git, so we create a .gitignore file. Note that this step is optional.

Next, we install the dependencies needed for this project to work. In the main project folder, we'll create a composer.json file. Then paste this in our composer.json file.

To install the Illuminate database, we add this to our composer.json:
“illuminate/database”: “5.1.8”,.

Now, our composer.json file should look like this:

We will now run these two composer commands in the same location as our composer.json file:

This will generate a vendor folder which we can add to gitignore (this is also an optional step).

Let’s add a config file for our database credentials.

In the main project directory, we create a file named config.php and define DB details in the Config.php file. Note that the values should be replaced with your own connection details.

Next, we create the schema for our app.

One thing to note before we create the schema for the tables in our database is that we can add timestamps to our schema.

The Eloquent ORM expects two timestamp columns if we want to enable timestamp operation on a particular table/model. They are the created_at and updated_at columns. If we enable timestamps for a model, Eloquent automatically updates these fields with the time when we create or update a record.

There is a third column called deleted_at. The deleted_at timestamp works differently, though. Eloquent has a soft delete capability which uses the deleted_at column to determine whether a record has been deleted. If you delete a record with the eloquent ‘delete’ function and you enable Soft Delete, the column is updated with the time of deletion. These deleted items can then be retrieved at any time.

In this app, we will be taking advantage of the timestamps, so we’ll use all three in our Schema creation.

Create tables with the following commands in MySQL:

### Users

We’ll proceed by creating files for models and controllers for our tables in the following locations:

• project_folder/app/models/question.php
• project_folder/app/models/upvote.php
• project_folder/app/models/user.php
• project_folder/app/models/database.php
• project_folder/app/controllers/questions.php
• project_folder/app/controllers/users.php

Open models/database.php with an editor.

First we create the Capsule:

In the file above, we initialize and set up the capsule with the constants defined in config.php, and then we boot eloquent.

The next step is to create a start script. This will be a file where everything that has to be run before our app works is run.

We create a start file in the location project_folder/start.php, and then in the file, require the Composer autoload file:

require ‘vendor/autoload.php’;

After that, we require config.php to get the credentials defined: require ‘config.php’;

Then we initialize the database class.

Your start.php should look like this:

Include start.php in your index.php as this will be our main file.

Our index.php file now looks like this:

Next, we can start working on our controllers and models. In project_folder/app/models/question.php, we add this:

Then in project_folder/app/controllers/questions.php:

In project_folder/app/controllers/answers.php, we do the same:

In the user model (project_folder/app/models/user.php), we add the following code to define our namespace, extend the Eloquent Model, and define the table name (protected $table) and what fields in the tables can be filled by mass creation (protected$fillable).

In the users controller (project_folder/app/controllers/user.php), we define our namespace and class as usual:

Then to create a user, in the users controller, we import the user Model namespace, use Models\User;, and then add a function to create the user.

Our user controller now looks like this.

Then in index.php we add these lines and run the app to create a new user.

To add a question we import the Question model namespace in the questions controller, and write a create_question function:

use Models\Question;

Then:

We have used Eloquent mass creation models to insert this record, but before it works, we need to permit those fields to be fillable, because Eloquent models guard against mass creation by default.

So we go to the question model and add the protected $fillable property to the class. protected$fillable = ['question','user_id'];

To run this, import the questions controller in index.php and call the create_question function statically:

use Controllers\Question;

Then create a question with a question and User Id as parameters:

$question = Questions::create_question("Have you ever met your doppelganger?",1); This returns a model object if successful. We will now run the index.php script with different entries to add more questions to the database. ## Task 3: Add an Answer to a Question In the answer model, we repeat the steps taken for question and user models by adding the code below: Then in the answers controller, we write these lines: Then in index.php, we can create an answer for the question with id 1 we added earlier, with user id 2. Don't forget to import the answers controller to index.php first. To prevent multiple entries, comment all other calls in index.php before running a new one. ## Task 4: Upvote an Answer This is pretty much the same steps we are used to. So we'll copy this into the Upvote model at project_folder/app/models/upvote.php. Then in the answers controllers, we import the Upvote Model namespace. use Models\Upvote; Then we create an upvote_answer function. In index.php, we can call the function with a dummy User ID to upvote the answer with id 1. $upvote = Answers::upvote_answer(1,14);

For tasks like this, we can use Eloquent relationships.

Types of relationships include one to one, one to many, many to many, etc.

When using these relations, Eloquent assumes a foreign key in the form modelname_id exists on the models. For this task, the relationship is a one-to-many relationship because a single question can own any amount of answers.

First we define this relationship by adding this function to our question model.

Then in the questions controller, we write a function to get questions with answers.

This retrieves the questions with their corresponding answers.

In index.php, we comment all other calls and run:

$all = Questions::get_questions_with_answers(); We can var_dump or print_r the $all variable to see the results.

This is a one to one relationship because one question has one user, so we add this to the question model.

Then we create a function in the questions controller and use the with function on the question model.

In index.php, comment all others and run this:

We can print the $one_question variable to see the results. ## Task 8: Count All Questions by a Particular User First we import the question model in the users controllers: use Models\Question; Then we write this function: In index.php, we comment other calls and add this line: $user_question_count = Users::question_count(1);

This returns an integer which is the number of questions that have been added by a user with id 1.

We can print the $user_question_count variable and run index.php to see the results. ## Task 9: Update Answer by User The concept of updating with the Eloquent ORM is pretty simple. First we find a record, and then we mutate and save. Now, in the answers controllers, we add this function: In index.php, we can comment all other calls, and update answer with id 1 like this: $update_answer = Answers::update_answer(1,”This is an updated answer”);

This returns a boolean value—true—if the update is successful.

## Task 10: Delete a Question (Soft Delete)

In this final task, we'll implement Eloquent SoftDelete.

First we tell the question model to use SoftDeletes by importing the SoftDeletes namespace, and then using the SoftDeletes trait in our class.

use Illuminate\Database\Eloquent\SoftDeletes;

Then after the class declaration line, we add this line:

use SoftDeletes;

Then we add deleted_at to the protected $dates property for the model. These are the required steps. protected$dates = [‘deleted_at’];

Our question model now looks like this:

Then we create the delete_question function in the questions controller.

Run in index.php:

\$delete = Questions::delete_question(1);

Congratulations! You just built a fully functional back end with Illuminate and Eloquent. And we didn't have to write so much code to achieve all this.

The code for this tutorial can be found on GitHub

## Conclusion

Illuminate also comes with the Query Builder which you can use for even more complex database queries and is definitely something you want to experiment with and use in your app.

The only thing missing in the standalone Illuminate Database is database migrations, which are a lovely feature of Laravel, and Lumen, the microframework by Laravel. You should consider using both in your apps to take advantages of the useful features they come with.

You can find out more about Eloquent on the Official Eloquent Documentation Page.