On Fri, 2006-07-14 at 19:48 +0200, Gerhard Killesreiter wrote:
Martin Afanasjew wrote:
Gerhard Killesreiter wrote:
Hi there!
Dropping both MySQL 3 and 4.0 would enable us to rewrite some parts of our SQL queries. The extend of this would need to be researched.
Dropping support outdated versions is fine as long as there are good technical reasons and I fully support this. Having said this I really would like to see some examples where Drupal would improve due to this change. I hope it's not just for the sake of dropping support...
Subselects might enable us to put two queries into one.
Sub-Selects can be beast, especially if you are sub selecting from a large table. They great for reporting, and moving data handling into the DB... I'm more interested in getting drupal to use views, and database constraints... dropping support for 3.23 is a raising our least common denominator and headed in the right direction.
I know that people will argue with "but there are so many ISPs that still run 3.23". ISPs that still run 3.23 after it has been retired by the supporting company are probably not worth the money you them.
3.23 is simply rock solid and as long as it is properly supported I can't see a reason for hosters to upgrade. Especially since almost all software (including Drupal) still supports it...
There will not be any security updates for 3.23 from MySQL AB. Enough reason to drop it.
Big +1, and ISP's and Control Panel developers will drop it as well if they don't have upstream support to cover their liabilities.