News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Justin Carmony's Blog:
PHP Design - Biggest Database Oversights
November 26, 2008 @ 14:14:56

Justin Carmony recently put together a blog post looking at the biggest database design oversights that PHP developers can make in their applications.

I've thought of some of the biggest oversights I've had when working with PHP and MySQL and put them in a list. This is my personal list, and I'm sure some people can think of some other oversights that belong on the list as well. This list is just for PHP & MySQL, not PHP and any database. I know many people like using software like Doctrine to allow switching between different database types. That is beyond the scope of this article.

He includes a list of five - not having a data access layer, designing for only one database connection, not including developer logging, having queries written in procedural code and no separation of reads and writes to the database.

0 comments voice your opinion now!
database design application oversights mysql list


blog comments powered by Disqus

Similar Posts

DevShed: Design Patterns and PHP 5

Allan MacGregor: Design Patterns in PHP: Singletons

php|architect: 2012 Impact Awards Voting Opened!

Wez Furlong\'s Blog: PDO MySQL slides from MySQLUC 2006

DevShed: Database Security: Guarding Against SQL Injection


Community Events

Don't see your event here?
Let us know!


introduction framework extension library example laravel5 version release opinion language security video podcast php7 series laravel voicesoftheelephpant api community interview

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework