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

Developer.com: What Web Application Stack Is Best for Me?

Ben Ramsey\'s Blog: OPML Reading List

IT Manager\'s Journal: Court library AMPs up

David Coallier's Blog: Simple DBAL, PHP5, Light, Fast, Simple.

Chris Hartjes' Blog: Where Are The Good Development Tools For PHP, Part II


Community Events





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


introduction tips deployment install release voicesoftheelephpant bugfix list opinion package laravel language symfony series api framework interview podcast library community

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