Menu
Community /Pin to ProfileBookmark
@NogDogDec 17.2008 — #Yes, InnoDB support transactions, MyISAM does not, I'm not sure about the other less-used engines.
MySQLi also supports transactions via the[url=http://www.php.net/manual/en/mysqli.autocommit.php]mysqli_autocommit[/url] (), [url=http://www.php.net/manual/en/mysqli.rollback.php]mysqli_rollback[/url] (), and [url=http://www.php.net/manual/en/mysqli.commit.php]mysqli_commit[/url] () methods.
I've not done much yet with PDO myself, but know a few people who use it regularly without any problems that I know of. You do have to keep your queries pretty generic, with the payoff being that your application becomes less closely tied to a specific DBMS. The downside, of course, is the inability to use any DBMS-specific features (or at least not easily), so it all depends on what your priorities are.
Mostly I've been using MySQLi lately due to its better support of newer/advanced MySQL functionality, as well as the OOP aspect. I often simply create a class extending MySQLi in order to build in some configuration and error-handling stuff directly with it.@NogDogDec 17.2008 — #[url=http://www.php.net/pdo]PDO[/url] (PHP Data Objects) is a "database abstraction layer" which provides a uniform interface to the database regardless of which DBMS is being used. In a nutshell, the idea is that if you decide to change from, say, MySQL to Postgre, the only thing you would need to change in your code is the DNS connection string, which ideally would mean you'd only need to change one line of code.
Probably the next step up, providing even more abstraction, is thePEAR MDB2 package , which goes further to provide portability between different DBMS's.
MySQL vs. MySQLi
Hit me. ?
I’m currently using the MySQL extension across all of my projects, but I now have a genuine interest in the “dark side” ?
So, who can persuade me to either side?
ayvegh
Sign in
to post a comment8 Comments(s) ↴
0
@NogDogDec 17.2008 — #Yes, InnoDB support transactions, MyISAM does not, I'm not sure about the other less-used engines.MySQLi also supports transactions via the
I've not done much yet with PDO myself, but know a few people who use it regularly without any problems that I know of. You do have to keep your queries pretty generic, with the payoff being that your application becomes less closely tied to a specific DBMS. The downside, of course, is the inability to use any DBMS-specific features (or at least not easily), so it all depends on what your priorities are.
Mostly I've been using MySQLi lately due to its better support of newer/advanced MySQL functionality, as well as the OOP aspect. I often simply create a class extending MySQLi in order to build in some configuration and error-handling stuff directly with it.
0
@NogDogDec 17.2008 — #Probably the next step up, providing even more abstraction, is the