Databases
StackOverflow2013
Postsdbo
POWhat's the best way to abstract the database from a PHP application?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat's the best way to abstract the database from a PHP application?
    primarykey
    data
    text
    <p>My question is how does one abstract a database connection from the model layer of an application? The primary concern is to be able to easily change from different types of databases. Maybe you start with a flat file, comma-delimited database. Then you want to move to a SQL database. Then later you decide an LDAP implementation would be better. How can a person easily plan for something like this?</p> <p>For a simple example, let's say you have a user with a first name, last name, and email. A very simple PHP class representing it might look like this (please ignore the problems with public instance variables):</p> <pre><code>&lt;?php class User { public $first; public $last; public $email; } ?&gt; </code></pre> <p>I have frequently seen where people have a DAO class which has the SQL embedded in it as such:</p> <pre><code>&lt;?php class UserDAO { public $id; public $fist; public $last; public $email; public function create( &amp;$db ) { $sql = "INSERT INTO user VALUES( '$first', '$last', '$email' )"; $db-&gt;query( $sql ); } } ?&gt; </code></pre> <p>My problem with strategies like this is when you want to change your database, you have to change every DAO class' create, update, load, delete functions to deal with your new type of database. Even if you have a program to auto-generate them for you (which I am not particularly a fan of), you would have to edit this program to make it work now.</p> <p>What are your suggestions for how to handle this?</p> <p>My current idea is to create a super class for DAO objects with its own create, delete, update, load functions. However, these functions would take arrays of the attributes of the DAO and generate the query itself. In this manner, the only SQL is in the SuperDAO class rather than being scattered about several classes. Then if you wanted to change your database layer, you would only have to change how the SuperDAO class generates the queries. Advantages? Disadvantages? Foreseeable problems? The good, the bad, and the ugly?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USstillstanding
    1. USMarshmellow1328
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat's the best way to abstract the database from a PHP application?
      1. USJhonny D. Cano -Leftware-
      1. VTFavorite
    2. VO
      singulars
      1. POWhat's the best way to abstract the database from a PHP application?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat's the best way to abstract the database from a PHP application?
      1. USStrae
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload