-
Notifications
You must be signed in to change notification settings - Fork 21
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
Migrate from ADODB to PDO #13
Comments
Woooooo! proceed with caution. :-) I can't imagine somethink like a "migration script", we (and lot of SIFO-projects, I think) are using ADODB methods in all of our Models (getAll, getRow, getOne, Execute, Autoexecute, etc.) Are there specific equivalents in PDO? |
A specific class ADODB to PDO that implements all this ADODB methods (getOne, getRow) ... but using PDO would be implemented |
Could be a solution. This AdoDBToPDO class + a migration manual would be great. :-) |
Agreed, I'll take a look at this Can you give me a list with the most used AdoDB methods? |
Most used models in ADODB: AutoExecute Less common, but present: BeginTrans There are more methods, but I don't think they are used at all (like sequences for mysql). Do not forget that there are many methods of Model, not related to adodb like nextQueryInMaster |
I did a first test replacing current version by 5.18 and it seems to work. The only thing to be fixed is the following notice, generated by the debug:
This is the internal variable that stores current SQL query. Fixing that I think we can migrate it and test in devel. |
UPDATE: ADODB keeps alive with PHP5 support (see: http://sourceforge.net/projects/adodb/). The last update is from June 2013 and current version is 5.18. SIFO is using 5.06 right now.
Multiple driver database feature will be lost per default (Mysql, postgresql, oracle...) and we will stick to Mysql when it comes to relational databases.
A class to maintain backwards compatibility could be created, or a migration script. I don't know which of them are more painful
The text was updated successfully, but these errors were encountered: