I see several problems with deprecating ext/mysql: - The extension is not broken. The problem is the bad usage. It can be used safely, and good developers have been doing so for ages, by creating php wrappers. In magic quotes, the work has been the opposite. The developers had been detecting the feature in php and *disabling* it.
- How many hosts/ISPs have mysqli installed? I don't have actual numbers, but it used to be much less common than ext/mysql, which means that unless they those customers won't be able to run the applications forced to migrate to mysqli. Yes, the customers should complain and get the extension enabled, but what will happen instead is that they will use outdated version X of WordPress, since that one works. So the problem really moves onto the CMS providers, do they support new php versions and drop customers in shared hosting, do they delay supporting the new php versions, or do they reimplement mysql_* in php? - A "magic porting script" has been mentioned on this thread. It is not on the docs, so it is really as if it didn't exist for the 99% of the population. Moreover, there is even a FAQ stating that there are no migration scripts right now: http://php.net/manual/en/faq.databases.php#faq.databases.mysql.deprecated It should be linked from every mysql page. - If you are sure your ext/mysql usage is safe, it is not possible to disable the warning for this functions but keep the other E_DEPRECATED. - I'm quite sure that there will be a number of problems where the replacements have issues, but they are unlikely to be fixed if not forced. For instance, I remember a php script using mysql that from reading the code, it shouldn't be working but it somehow did. Completely unmaintained, of course. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
