₦airaland Forum

Hi guys,

I just dived into Object-Oriented programming style for PHP from procedural.

The issue i have now is, the functions within the Classes don't get to see the database connection Variable and i have to include it into each functions.

What other way can i do this without repeating the connection code for each function?

Also apart from the classes, the code i have been writing look like ordinary procedural form of writing and i've been wondering if i'm doing the right thing. is it normal for the code written in OOP style to look much like Procedural?


i have downloaded different PHP source code from free source codes site in order to check if i'm doing the right thing. but all the codes i have downloaded so far are written in procedural, probably by learners like me.
if you have a fully functional source code(like a blog) written in OOP that you can give out, i won't mind getting it.

Thanks.

For the first question, i discovered by passing the connection variable as an argument to the functions, i can use them without creating a new instance for the function.

Is this good programming practice?

Best approach: Use a singleton class, use static functions, declare your class constructors as private: if you don't understand the reason you should do those then you are better of using globals (not the best approach)

global $conn = mysqli_connect ("localhost", "root", "", "database";
global $conn;

function someFunction () {
global $conn;
$result = mysqli_query ($conn, "SELECT * FROM examples)
}

or something as basic as:

class Db
{
    private static $conn;

    public static function getObject()
    {
        if (!self::$conn)
            self::$conn = new mysqli("localhost", "root", "", "database";

        return self::$conn;
    }
}

function someFunction () {
$result = mysqli_query (Database::$conn, "SELECT * FROM examples)
}

Ayemileto:
For the first question, i discovered by passing the connection variable as an argument to the functions, i can use them without creating a new instance for the function.

Is this good programming practice?

Creating new instance for $conn each time you need it Is a bad idea, no scalabilty, u might even end up creating more connections than your server can handle

javascriptDev:
Best approach: Use a singleton class, use static functions, declare your class constructors as private: if you don't understand the reason you should do those then you are better of using globals (not the best approach)

global $conn = mysqli_connect ("localhost", "root", "", "database";
global $conn;

function someFunction () {
global $conn;
$result = mysqli_query ($conn, "SELECT * FROM examples)
}

or something as basic as:

class Db
{
    private static $conn;

    public static function getObject()
    {
        if (!self::$conn)
            self::$conn = new mysqli("localhost", "root", "", "database";

        return self::$conn;
    }
}

function someFunction () {
$result = mysqli_query (Database::$conn, "SELECT * FROM examples)
}

Thanks. I think the second one should be called with Db::$conn

javascriptDev:
Creating new instance for $conn each time you need it Is a bad idea, no scalabilty, u might even end up creating more connections than your server can handle

Thanks. What about the code looking much like procedural? Is it normal?

Ayemileto:
Thanks. What about the code looking much like procedural? Is it normal?

perfectly normal if you are just starting out with oop php. But try more frequently to group those ”procedures” into functions and wrap them in classes. That way you use mostly objects in your app

Ayemileto:
Thanks. I think the second one should be called with Db::$conn

yes, my bad

javascriptDev:
perfectly normal if you are just starting out with oop php. But try more frequently to group those ”procedures” into functions and wrap them in classes. That way you use mostly objects in your app

Thanks bro.