May 24, 2008 in Feedback
We know ipb has the feature to allow it to interact with other databases via the seperate classes available which are shipped with the current version of ipb. This as we know can lead to create extensive code and code duplication to change queries to work with other databases. Has the thought crossed your minds to make use of the new ( and rather nice ) PDO extension which was added to php?
The PDO object has the ability to handle error exceptions which is a great advantage when debugging and creating a more seemless user experiance. the exec method is also very nice (in that when you run a update, insert, delete query it returns how many rows effected). This can as well as how some of the other functions run can save on overhead as they do multiple normal day to day things (which would require two or more function calls in the current method ) in one.
Using PDO wouldn't change the fact that we'd still need to duplicate and separate the queries.
What we are working at for 3.0 instead is adding more support for some of the common database-specific functions we use. For instance, we have group by, from_unixtime, date_format, right, left, substring, is null, is not null, concat, instr, and a few others supported directly in the drivers now (these are mysql functions/syntax, but we're updating the other drivers to properly support the equivalents too). The mysql_queries.php file no longer exists by default. :)
This topic is now archived and is closed to further replies.
Started Yesterday at 01:29 AM
Started October 4
Started Wednesday at 05:56 PM