Tibaso

At the moment I am writing an application that supports plugins. Every plugin implements an interface so that the main application can control the plugin with the interface methods. There could be plugins that need a database connection and others that do not. What I am doing at the moment is loading every plugin with a __construct($databaseHandler). For plugins that don't need a database connection this is a little overhead. I could also use a Singleton or something else "staticish" so that the plugin can get the database instance whenever it wants, but then the plugin can only be used for my application where this specific Singleton is present and maybe I would like to use the plugin for other purposes later in another environment without changing it. Do you have any better ideas or how do you normally manage your database connections?

*push*

Does noone know what the new class SQLite3 is for?

No, I am not confused, PHP 5.3 introduced the new class SQLite3: http://php.net/manual/de/book.sqlite3.php I am working already for quite a while with PDO and sqlite3 but now I was reading about the new php class SQLite3 and it works almost the same like PDO except it is only for SQLite3 databases and can not wrap other databases. So since at the moment I am writing an application that uses only sqlite, I am wondering if there is any advantages to use SQLite3 instead of PDO.

Hi, I'm new to this board. My first question: Is there any reason to use the new PHP 5.3 class SQLite3 instead of PDO?