Hi,

im about to go about putting together a DB fucntion class, and im wondering about something.. i have a game script and it has two db class files one for mysqli and one for mysql and it includes them for which ever one is set so if u tell it it is mysqli it uses that etc... but why is it worth it?

and how could it be better done?

Hey, Dan!

Why is what worth it? Building a db wrapper class?

Many reasons: Flexibility, easy to update and edit the way your sql queries are handled, makes coding easier.

If you want to make a wrapper for your wrapper, so that you can easily switch between different databases, it would be best to create an abstract class for the wrapper of your wrappers ( if that makes sense )

abstract db class
-> mysql wrapper class
-> postgresql wrapper class

If you would like, I can code you up a simple example of a basic mysql wrapper for php.

o.0 ok... erm wrong end of stick.

i know why its a good idea to sue Classes (only just got the courage to attempt them...)

what i ment was having two classes one with all the mysql_ functions (for mysql 4 < and php < 4) and a mysqli_ funcs for php 5> and mysql 5>


anyways im doing it now and its not working...

i have the connection part changed over and it is connecting, but none of my queries are working... why?

(at the moment the queries are NOT using the class)

but shouldnt they still work?

ALSO when i make a query ($db->query()) do i have to have global $db; inside the function or is there a way to have it globalised by default?

On a basic level, a class consists of methods and properties.

Methods are simply the functions, and properties are basically the global variables inside of the class.

Methods and properties can be accessed from within the class by using $this

class myClass
{
var $myProperty = 2;

function myMethod ( )
{
$result = $this->myProperty * 3;

return $result;
}

function anotherMethod ( )
{
$result = $this->myMethod ( );

echo $result;
}
}