{"id":1533,"date":"2018-01-19T19:22:57","date_gmt":"2018-01-19T19:22:57","guid":{"rendered":"http:\/\/goofy-trucks.flywheelsites.com\/value-objects-and-data-access-objects-with-php-4-2-x\/"},"modified":"2018-01-19T19:24:51","modified_gmt":"2018-01-19T19:24:51","slug":"value-objects-and-data-access-objects-with-php-4-2-x","status":"publish","type":"post","link":"https:\/\/phpbuilder.com\/value-objects-and-data-access-objects-with-php-4-2-x\/","title":{"rendered":"Value Objects and Data Access Objects with PHP 4.2.x"},"content":{"rendered":"
\n
\n
By Geno Timlin<\/div>\n
on June 1, 2004<\/div>\n<\/p><\/div>\n
\n

Introduction<\/h2>\n
\nMy real job involves working with J2EE applications at this time. It pays the bills.
\nI’ve worked with ASP in the past and have recently (2003) gotten more into working with PHP.
\nMost of my sidework these days is data driven PHP\/MySQL web sites. It’s unfortunate that
\nsidework doesn’t pay the bills, because I have found PHP to be a very powerful programming platform.
\nMy attempt here is to apply some principles and concepts that I have learned in my work with
\nJ2EE into my work with PHP.<\/div>\n

Value Objects<\/h2>\n
\nThe purpose of a Value Object is to represent a business entity. In it’s simplest form, a
\nVO is a simple data mapping class that mirrors the entity as it exists in the database. A
\nmore complex VO may incorporate other functionality in its methods. For example, a VO may
\nhave a method that transforms it’s data into an XML node or a VO may be able to read it’s
\ndata from an HTML form. The one thing the VO doesn’t have to worry about is the database.
\nThe main purpose of the VO is to store data as the data comes in and out of the database.<\/div>\n

Data Access Objects<\/h2>\n
\nData Access Objects act as the middle man between the database and the Value Objects.
\nThe base DAO class knows specifically how to talk to the database. The base DAO knows which
\ndatabase is being used, what kind of database it is and whether it’s supposed to be working with
\nmysql_*, mssql_* or pg_* methods. The base DAO is essentially the Data layer or Model part of the MVC
\nThe DAO classes that extend the base DAO class can use the base DAO’s methods to select, insert,
\nupdate and delete data. The extended DAO classes don’t have to worry about whether they are talking
\nto a MySQL database or a PostGreSQL database. If you switch from MySQL to PostGreSQL, you can change
\nthe base DAO class and the extended DAO’s will not be affected. The extended DAO’s are the business
\nlogic layer or the Controller part of the MVC.<\/div>\n
\nDAO’s and VO’s Working Together<\/div>\n
\nThe extended DAO classes utilize the VO’s to retrieve data and update data. If you want a single
\nrow of data from the database, based on the record’s primary key value, the extended DAO will
\nhave a method that returns a single VO. The extended DAO will have a method that returns an array of
\nVO’s if you want more than one row of data. The extended DAO handles inserts, updates and deletes
\nwith methods that take a single VO as an argument.<\/div>\n
\nThe Application<\/div>\n
\nIn the example code, I’m presenting some of the functionality of a simple auto sales web site.
\nWe’ll look at the vehicles that are stored in the database. The database is a MySQL database and
\nthe vehicles table is created with the following properties:<\/p>\n
\n
\nCREATE TABLE `vehicles` (\n`vehicleid` INT NOT NULL AUTO_INCREMENT,\n`year` VARCHAR( 4 ) NOT NULL ,\n`make` VARCHAR( 25 ) NOT NULL ,\n`model` VARCHAR( 25 ) NOT NULL ,\n`color` VARCHAR( 25 ) NOT NULL ,\n`price` DOUBLE NOT NULL ,\nPRIMARY KEY ( `vehicleid` ) \n);\n<\/pre>\n<\/div>\n<\/div>\n
<\/p>\n
\n
1<\/div>\n
| <\/div>\n
2<\/a> <\/div>\n
| <\/div>\n
3<\/a> <\/div>\n
| <\/div>\n
4<\/a> <\/div>\n
| <\/div>\n
5<\/a> <\/div>\n
| <\/div>\n
6<\/a> <\/div>\n
| <\/div>\n
7<\/a> <\/div>\n
Next Page \u00bb<\/a><\/div>\n<\/div><\/div>\n
<\/p>\n