When working with CakePHP it is important to remember "Convention over Configuration." If you start from the bottom, or back end, the database, and work your way forward correctly, CakePHP will do much of legwork for you, saving you tons of redundant and repetitive work.
If you don't, there are almost always ways to make things work the hard way. An example of this is the relationships between tables. If you name your database tables and fields following CakePHP convention, it becomes trivial to set up relationships between them.
Now we're going to work on storing our Session information in the database.
Now that your application is up and running, it is time to build your data store and interface with that data. We have two options here: We can create the database tables using Migrations or directly in the database, either through the database interface, a web interface, or an IDE interface.
