Search the Community
Showing results for tags 'mvc'.
Found 2 results
Been studying your book for a while and noticed it is not too much different from the 4th edition. The book's using mysqli_ for database connection, and the php is still version 5.some. Meanwhile, php 7 has come to life and the pdo is ubiquitous nowadays. As well as MVC and more or less object oriented approach in general. Some books i know of (i'm not sure if i can mention them here) went through this and even their hands-on practice evolved from developing a simple CMS to an almost framework-like application. So, my question is: will you update your PHP & MySQL series?
Hi all, I used these forum long ago and I can no longer remember my login creds..... anyway this question isn't really about this book, but I felt it would go best in the "Quickpro" arena. I'm wondering how you MVC users approach data handling. I'll create a simple scenario - 3 Tables (a, b and c) - Table a joins to table b which joins to table c - I have a query which selects all "a" rows and how many "b" and "c" rows match each "a" row. I steering clear of any ORM's for now and I'm using ->fetchObject in PDO mapping the data to the "a" model. The Problem The "a" model doesn't have an attribute for "total b rows" or "total c rows", is it ok by MVC law to store this data in the "a" object or should it be stored somewhere else, if so where? Thanks for reading and hopefully replying Simon