Comments on: PHP Design – Biggest Database Oversights

By: Eoin

Eoin — Fri, 22 Jan 2010 12:50:35 +0000

Great.

I couldn’t live without a MySqlDAL-type class these days.

One thing that I just learned was with designing a $db->insert() method, I should pass it an array with keys and values. So simple, I should have thought about it years sooner

Until now I had been constructing the INSERT statement in each set() method of my objects’ classes.

By: Gabriel

Gabriel — Fri, 22 Jan 2010 12:08:10 +0000

@Cassie: The simple DAL has no error checking. In your real DAL you would throw an exception when an error occurs. The stack trace of the exception then gives clues on where the error occured.

By: hqlong

hqlong — Fri, 22 Jan 2010 07:04:40 +0000

Your bring up good point,but general use framework or pdo. thank you your share!!

By: PHP Design – Biggest Database Oversights – Justin Carmony’s Blog « Netcrema – creme de la social news via digg + delicious + stumpleupon + reddit

Fri, 22 Jan 2010 06:41:17 +0000

[...] PHP Design – Biggest Database Oversights – Justin Carmony’s Blogjustincarmony.com [...]

By: Athomeinthenoise

Athomeinthenoise — Thu, 14 Jan 2010 22:14:24 +0000

Nice site, I was just talking about it with my friends last nite. It also looks really nice in the Blackberry browser, which is rare. Good job!

By: Greg

Greg — Wed, 23 Dec 2009 15:35:31 +0000

use CodeIgniter or another framework. Will solve most of your issues by default.

By: Daniel

Daniel — Thu, 12 Nov 2009 13:24:56 +0000

On #4: Keeping it DRY, you ought to put repeatedly used stuff in an extra, included file, anyway.

And if you look at it from the other side: what if your boss wants to change links only in SOME places? You’d have to write multiple classes or introduce some parameters. I leave it to you to decide what’s better.

By: Stay Weight Loss

Stay Weight Loss — Thu, 20 Aug 2009 08:32:11 +0000

Weight Loss Pills, weight loss program, quick weight loss, stay fit…
weight loss tips

By: Cassie

Cassie — Thu, 30 Jul 2009 11:44:24 +0000

Apologies if someone has mentioned this already, but referring to oversight 1, this is the way the previous developer at my company coded our system.

The problem is, anytime that a query the error comes from the same line (obviously, because its run from the same line). This is really frustrating, because you have no way of telling where the real error is coming from.

By: computer Service toronto

computer Service toronto — Wed, 29 Jul 2009 05:19:48 +0000

I got it Thanks