-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace mysql with pdo #11
Comments
I highly recommend doing this. That way, you won't need to use addslashes, magic_quotes, and the auto IP ban thingy for "UNION SELECT". Don't know if you been up to update with Acmlmboard 2, but it now has completely dropped the magic_quotes dependency as all dynamic queries are now prepared queries. Also, when you have keys in a string, you should put single quotes around the array and braces around the variable and the brackets. For example, Good luck. |
I am well aware of these issues -- the majority of the code dates back to 2001. P.S. I do not appreciate you sending death threats to members, so kindly go away, forever. Thanks. |
OK, fine. She was a former friend of mine who stabbed me in the back months ago so I personally don't care. |
while I can only recommend prepared queries, the portability argument of PDO is moot: PDO can handle multiple database systems, but that's about it, it doesn't cover the syntax differences in more complex/specific SQL queries |
For what I've tested in my fork, it is possible to have an almost compatible PDO class that can replace the MySQL one. "Almost", because:
Though converting also means replacing the remaining raw mysql_ commands to calls to the mysql class, because mixing PDO and mysql_ commands obviously doesn't do any good. |
Right now there is a mixture of raw mysql_...() commands and commands run through a mysql pseudo-class. these should be replaced with a pdo-based class (and queries redone to use prepared statements).
The text was updated successfully, but these errors were encountered: