Sorry not to be more clear. I intended to contrast what I understand to be two separate modules, namely DBI and DBD::mysql. At the moment I use the former, which is v straightforward and easy to learn; but (so far as I can make out) unlike DBD::mysql it doesn't support MySQL transactions. If DBI does support MySQL transactions I'd be glad to hear of it! But as you can see from the thread I linked to, my interim conclusion is that it doesn't, whereas DBD:mysql does. My main point is, that if I start out on a project like this in future, I'll make sure I use a DBMS / driver combo that lets me do transactions.
§ George Sherston | [reply] |
DBI does not support MySQL.
DBD::MySQL is the module that DBI uses to support MySQL.
DBD::MySQL is only able to support transactions as far as MySQL can, ie afaik not at all.
Maybe you are thinking of the MySQL module, an old (and obsoleted) perl4 (?) compatibility mode module?
Appendix B of the Cheeta book describes the differences between the different database systems that the DBI-drivers support (or to be more correct: describes the way that the drivers implement and/or support the many DBI features, eg date-formats, transaction handling, blob handling), and is definitely worth reading if you use the DBI.
| [reply] |
actually, i believe that the newest version of mysql does have soome limited transaction capability, if you use the right extensions. i don't use it in that capacity, so i can't comment on the implementation beyond suggesting that anyone interested should check the various mysql-oriented sites.
| [reply] |
