Hi there! MySQL AB (the company behind our most used database) has announced a change in support options for their database products. http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year. I therefore propose that we formally drop support of MySQL 3 as of Drupal 4.8 which will appear later this year. MySQl 4.0's active support will end the last of September, we could consider dropping support for it too. Extended support will run until the end of 2008. 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. 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. Cheers, Gerhard
On Fri, July 14, 2006 11:06 am, Gerhard Killesreiter said:
Hi there!
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year.
I therefore propose that we formally drop support of MySQL 3 as of Drupal 4.8 which will appear later this year.
MySQl 4.0's active support will end the last of September, we could consider dropping support for it too. Extended support will run until the end of 2008.
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.
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.
Cheers, Gerhard
+1 on dropping MySQL 3.x. It's about as outdated now as PHP 3 is. However, 4.0 is still in active use. The web host that my company does nearly all its hosting through is using 4.0 still, much to my dismay. (We don't do Drupal work, but it is a non-small host. FutureQuest.) While I'd love to be able to use MySQL 4.1 features (subselects are the first thing that come to mind), I don't know if the market penetration for 4.0 is low enough yet that we can get away with it. We support PHP back to 4.3.6, even though that's several years old and 4.3.10 is the minimum I'd recommend for anyone these days, if not 4.4. Does anyone have any decent numbers on MySQL's 4.0's active use? --Larry Garfield
Does anyone have any decent numbers on MySQL's 4.0's active use?
The main difference between 4.0 and 4.1 is support for database charsets, which is "mandatory". That's the main reason why many webhosters from Czech Republic, Slovakia and other countries using diacritics stick on 4.0. It's just very difficult and time consuming to convert all databases... Jakub Suchy
On Jul 14, 2006, at 9:06 AM, Gerhard Killesreiter wrote:
Hi there!
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year.
I therefore propose that we formally drop support of MySQL 3 as of Drupal 4.8 which will appear later this year.
MySQl 4.0's active support will end the last of September, we could consider dropping support for it too. Extended support will run until the end of 2008.
If we could assume 4.1 or higher for 4.8 that would be very useful. 4.7 will work with 3.23 and 4.0 for at least 6 months giving folks plenty of time and options. I'll look into a what standards are support in MySQL 4.1 that would be compatible with other DBs that we could use. Kieran
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.
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.
Cheers, Gerhard
Op vrijdag 14 juli 2006 18:06, schreef Gerhard Killesreiter:
MySQl 4.0's active support will end the last of September, we could consider dropping support for it too. Extended support will run until the end of 2008.
For others making the same reading mistake as me: Dropping 4.*0* means that we will still support 4.1 and other 4.X-es, where x > 0; Just a note. Bèr (who feared for a minute he was forced to go to MySQL 5.x)
Hi, It would be great if we could see how many times a project has been downloaded in the project administration section. introfini
It would be great if we could see how many times a project has been downloaded in the project administration section.
Please review the patch to this issue, which would introduce a browsing option based on how many sites actually use modules: http://drupal.org/node/66013
Gerhard Killesreiter wrote:
Hi there!
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year.
This is a really strange document. According to it would be worth dropping MySQL 4.1 as well since they stop supporting it by the end of this year. And if you compute the time between GA (general availability) and end of active support it gets shorter with every release. I really don't understand why this is the way it is...
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...
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... Martin
Martin Afanasjew wrote:
Gerhard Killesreiter wrote:
Hi there!
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year.
This is a really strange document. According to it would be worth dropping MySQL 4.1 as well since they stop supporting it by the end of this year. And if you compute the time between GA (general availability) and end of active support it gets shorter with every release. I really don't understand why this is the way it is...
This is explained on the first page of the document.
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.
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. Cheers, Gerhard
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.
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.
While it's quite OK to drop MySQL 3.x support (even Debian stable has 4.0) but dropping 4.0 is absolutely out of question. Despite even Debian stable has the mysql-server-4.1 package and all, as someone already mentioned it's quite a big jump that not everyone will make. There are few features of MySQL we could utilize but well, at least http://drupal.org/node/38297 could be done, we need to move (part of) pager_query to database.??sql.inc . The relatively small number of new features also indicate that the big change is between 4.1 and 4.0 and not between 3.x and 4.0. The bigger advantage will be somewhat 'behind the curtains' -- we can rely on the query cache somewhat more.
+1 on dripping 3.23 for Drupal 4.8. Keep 4.0 for the time being. Is there any way we can get statistics breakdown on MySQL version used? Would be nice to add that in our phone home feature in drupal.module (While we are at it, database type, database version, php version, OS type as well).
On Jul 15, 2006, at 8:10 AM, Khalid B wrote:
Is there any way we can get statistics breakdown on MySQL version used?
I think the real question is what will the statistics be when security patches stop being released for MySQL 4.0. If the database is not going to be secure for free in December 2006 should we be support it? Kieran
On Jul 15, 2006, at 8:37 AM, Kieran Lal wrote:
On Jul 15, 2006, at 8:10 AM, Khalid B wrote:
Is there any way we can get statistics breakdown on MySQL version used?
I think the real question is what will the statistics be when security patches stop being released for MySQL 4.0. If the database is not going to be secure for free in December 2006 should we be support it?
4.0 will be supported until 2008 apparently. Kieran
Kieran
Gerhard Killesreiter wrote:
Hi there!
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
Given this announcement, I agree completely with Gerhard. Let's drop support for MySQL 3.x and consider dropping support for 4.0 as well with Drupal release 4.8. ..chris
On Jul 14, 2006, at 5:27 PM, Chris Johnson wrote:
Gerhard Killesreiter wrote:
Hi there! MySQL AB (the company behind our most used database) has announced a change in support options for their database products. http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
Given this announcement, I agree completely with Gerhard. Let's drop support for MySQL 3.x and consider dropping support for 4.0 as well with Drupal release 4.8.
Just to be clear, extended support (security updates and fixes for severity level 1 bugs) for MySQL 4.0 does extend through the end of 2008. So the lack of security updates argument only applies to 3.x. Ray
On Fri, 14 Jul 2006, Ray Zimmerman wrote:
On Jul 14, 2006, at 5:27 PM, Chris Johnson wrote:
Gerhard Killesreiter wrote:
Hi there! MySQL AB (the company behind our most used database) has announced a change in support options for their database products. http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
Given this announcement, I agree completely with Gerhard. Let's drop support for MySQL 3.x and consider dropping support for 4.0 as well with Drupal release 4.8.
Just to be clear, extended support (security updates and fixes for severity level 1 bugs) for MySQL 4.0 does extend through the end of 2008. So the lack of security updates argument only applies to 3.x.
Ray
And many distros are stuck witih 4.0, including RHEL 4. I think requiring 4.1 would be a royal pain for thousands of users, no? John ---- aim/yim/msn/jabber.org: johnjosephbachir 713.494.2704 irc://irc.freenode.net/lyceum http://lyceum.ibiblio.org/ http://blog.johnjosephbachir.org/
On 14 Jul 2006, at 23:27, Chris Johnson wrote:
MySQL AB (the company behind our most used database) has announced a change in support options for their database products. http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
Given this announcement, I agree completely with Gerhard. Let's drop support for MySQL 3.x and consider dropping support for 4.0 as well with Drupal release 4.8.
Small remark: please be careful not to refer to the next Drupal version as "Drupal 4.8". If you want to use version numbers, write "Drupal 4.8/5.0". Thanks! -- Dries Buytaert :: http://www.buytaert.net/
Gerhard Killesreiter wrote:
Hi there!
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year.
I therefore propose that we formally drop support of MySQL 3 as of Drupal 4.8 which will appear later this year.
MySQl 4.0's active support will end the last of September, we could consider dropping support for it too. Extended support will run until the end of 2008.
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.
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.
A lot of service providers run Debian, which has recently dropped security support for the old stable (woody) distribution that shipped with MySQL 3.23. http://www.debian.org/News/2006/20060601 The current stable (sarge) distribution has been released for about a year now, includes both MySQL 4.0 and 4.1, and support for this release will probably continue for a couple of years (depending on when etch is released)
For whatever it's worth, I would support dropping 3.23 and 4.0 support. On 7/14/06, Antony Simmonds <antony.simmonds@manukau.ac.nz> wrote:
Gerhard Killesreiter wrote:
Hi there!
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year.
I therefore propose that we formally drop support of MySQL 3 as of Drupal 4.8 which will appear later this year.
MySQl 4.0's active support will end the last of September, we could consider dropping support for it too. Extended support will run until the end of 2008.
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.
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.
A lot of service providers run Debian, which has recently dropped security support for the old stable (woody) distribution that shipped with MySQL 3.23. http://www.debian.org/News/2006/20060601
The current stable (sarge) distribution has been released for about a year now, includes both MySQL 4.0 and 4.1, and support for this release will probably continue for a couple of years (depending on when etch is released)
-- Prometheus Communication http://www.prometheuscommunication.com Communicate or Die: American Labor Unions and the Internet http://www.communicateordie.com
On 14 Jul 2006, at 18:06, Gerhard Killesreiter wrote:
MySQL AB (the company behind our most used database) has announced a change in support options for their database products.
http://www.mysql.com/company/legal/mysql_lifecycle_policy.pdf
According to this document, the active support for MySQL 3.23 will end at the last of this month (ie on two weeks) and the extended support will end on the end of this year.
I therefore propose that we formally drop support of MySQL 3 as of Drupal 4.8 which will appear later this year.
Let's drop support for MySQL 3.*. Let's NOT drop support for MySQL 4.0 -- as mentioned by others, it will continue to be supported for a number of years. Thanks for pointing us to that document, Gerhard. -- Dries Buytaert :: http://www.buytaert.net/
participants (17)
-
Antony Simmonds -
Bèr Kessels -
Chris Johnson -
Darrel O'Pry -
Dries Buytaert -
Gerhard Killesreiter -
introfini -
Jakub Suchy -
John Joseph Bachir -
Karoly Negyesi -
Khalid B -
Kieran Lal -
Larry Garfield -
Martin Afanasjew -
Nedjo Rogers -
Ray Zimmerman -
Steve Dondley