Hi John, without seeing the specific errors, I can't really answer your first question.
This compatibility library covers most of the commonly used deprecated mysql_* functions. It doesn't yet have complete coverage of all mysql_* functions. There is also some subtlety about the implementation of mysql_connect, which isn't totally backwards compatible in the case where you have multiple database connections open at the same time. We intend to fix this but it's quite a complex issue and we just haven't got the time to tackle it right now - this is a free library and as you can imagine, paid projects have to take precedence. The library also covers ereg* and split functions. There may well be other areas of incompatibility between PHP 5.3 and 5.6, and no, this library doesn't address them at all. It's not intended as a blanket backwards-compatibility fix. It's primarily intended to ease the transition away from deprecated mysql_* functions.
You can see a list of the mysql_* functions that haven't yet been implemented in the README at the bottom of https://github.com/kitserve/php7-compat. If you search your codebase for these functions, you will know if there are any that need to be implemented. You will need to use a PHP backwards compatibility checker such as https://github.com/PHPCompatibility/PHPCompatibility to pick up other potential issues. Since version 7.0, PHP publishes a full list of backwards incompatible changes for each release, but unfortunately these weren't published for the versions you're looking at.
As to the second question, yes, you could fairly easily add in other overrides. Either create a separate library that follows the same principles, or fork the library and add in the extra features. We would of course appreciate if you contributed any changes back so that everyone can benefit from them.
I hope that this is helpful to you. If you find that you need more backwards compatibility fixes and wish sponsor us to develop them as part of this library, please feel free to contact us using our contact form (link at the top right of the page). Thanks!
Hi John, without seeing the specific errors, I can't really answer your first question.
This compatibility library covers most of the commonly used deprecated
mysql_*functions. It doesn't yet have complete coverage of allmysql_*functions. There is also some subtlety about the implementation ofmysql_connect, which isn't totally backwards compatible in the case where you have multiple database connections open at the same time. We intend to fix this but it's quite a complex issue and we just haven't got the time to tackle it right now - this is a free library and as you can imagine, paid projects have to take precedence. The library also coversereg*andsplitfunctions. There may well be other areas of incompatibility between PHP 5.3 and 5.6, and no, this library doesn't address them at all. It's not intended as a blanket backwards-compatibility fix. It's primarily intended to ease the transition away from deprecatedmysql_*functions.You can see a list of the
mysql_*functions that haven't yet been implemented in the README at the bottom of https://github.com/kitserve/php7-compat. If you search your codebase for these functions, you will know if there are any that need to be implemented. You will need to use a PHP backwards compatibility checker such as https://github.com/PHPCompatibility/PHPCompatibility to pick up other potential issues. Since version 7.0, PHP publishes a full list of backwards incompatible changes for each release, but unfortunately these weren't published for the versions you're looking at.As to the second question, yes, you could fairly easily add in other overrides. Either create a separate library that follows the same principles, or fork the library and add in the extra features. We would of course appreciate if you contributed any changes back so that everyone can benefit from them.
I hope that this is helpful to you. If you find that you need more backwards compatibility fixes and wish sponsor us to develop them as part of this library, please feel free to contact us using our contact form (link at the top right of the page). Thanks!