I strongly suggest that you actually try PDO and fully understand it before you go off on a tangent saying it's not good, then as an example you point out something completely obvious such as that MySQL has other commands than MsSQL...
Of course they are different, they are DIFFERENT query languages.
lol, i used PDO a while. ofc it has even strong aspects, like the preparing statements and the auto escaping of inputs to avoid injections.
but results shown, PDO is slow. to validate my inputs its running faster by simply throwing inputs into static validation class methods instead of fully using PDO.
to be able to prepare statements, i would use mysqli instead of mysql.
in case of mssql, i would use sqlsrv functions (not mssql, its outdated). it even supports all u need.
transactions/commits included lol.
there are just two good points why ppl should use PDO instead of providing regular database drivers:
- the independent fact of SQL... i agree its dump to think this is a good point, but actually its a reason for me (hard but possible if u spend much time to care about SQL differences and handle them), however it mostly fails on that. SQL isnt made for that like u said.
- you dont need to learn other functions if u switch the database, the rewriting is even faster
so in conclusion, if u need an application that uses more database types (like a cms where the user says which db type he/she wants), or if u are simply lazy and just want to learn PDO functions (unneccessary, most functions are almost the same named, you got references), its fine to use PDO, if u can live with the lost speed tho.
(even if my application uses 2 different database types, i would rather build two data access layers instead of switching to PDO, tbh)
