Fundamental MySQL changes in Drupal 6 (six)
Hi, After a little chat with Dries on #drupal : The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL). This will allow us to use more ANSI SQL constructs like subqueries. Life is beautiful. Regards NK
Just to clarify, version 4.1.1 will be safe then? On 11/12/06, Karoly Negyesi <karoly@negyesi.net> wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
This will allow us to use more ANSI SQL constructs like subqueries.
Life is beautiful.
Regards
NK
-- Prometheus Communication http://www.prometheuslabor.com Communicate or Die: American Labor Unions and the Internet http://www.communicateordie.com
Now if only some web hosts will actually bother to drop MySQL 4.0... Even Debian has dropped it for god's sake! :-) On Sunday 12 November 2006 14:38, Karoly Negyesi wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
This will allow us to use more ANSI SQL constructs like subqueries.
Life is beautiful.
Regards
NK
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Just the other day, I had someone ask me to make a module work on MySQL 3.23, and I pushed back saying sorry, can't do. It was a subselect that was needed. As far as dropping 4.0, I am fine with that, as long as 4.1 remains in 6.0, just like Steven asked for clarification above.
On Sun, 12 Nov 2006, Karoly Negyesi wrote:
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
This will allow us to use more ANSI SQL constructs like subqueries.
Life is beautiful.
Great. Not only subqueries but we can also build on proper encoding support in the database layer, which is great news. Gabor
Cool! My hosting company (they provide cPanel hosting) finally upgraded to MySQL 4.1 a few weeks ago. I'm guessing that more and more hosting companies are doing the same. Dropping 4.0 support from Drupal will untie us from many chains and shackles. Jaza. On 11/13/06, Karoly Negyesi <karoly@negyesi.net> wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
This will allow us to use more ANSI SQL constructs like subqueries.
Life is beautiful.
Regards
NK
As a point of clarification, what exactly does dropping 4.0 (compared to 4.1) buy us? I'm familiar with the differences between 4 and 5, but less knowledgeable about 4.0 vs. 4.1. As someone who would like to see more logic moved to the database layer, I'm very interested in what shackles we can escape. Cheers, -Mark On 11/12/06, Jeremy Epstein <jazepstein@gmail.com> wrote:
Cool! My hosting company (they provide cPanel hosting) finally upgraded to MySQL 4.1 a few weeks ago. I'm guessing that more and more hosting companies are doing the same.
Dropping 4.0 support from Drupal will untie us from many chains and shackles.
Jaza.
On 11/13/06, Karoly Negyesi <karoly@negyesi.net> wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
This will allow us to use more ANSI SQL constructs like subqueries.
Life is beautiful.
Regards
NK
The big things I'm aware of are subselects and unicode character sets. The REALLY big stuff like stored procedures came about in MySQL 5, and I don't think we can require that for some time yet. I believe this is the relevant change log: http://dev.mysql.com/doc/refman/4.1/en/news-4-1-0.html Out of curiosity, I know we discussed dropping 4.0 support for Drupal 5 a while back on this list, and reasons were given not to. Why the sudden change for Drupal 6, and why was it discussed in IRC instead of on the list? On Sunday 12 November 2006 21:21, Mark Fredrickson wrote:
As a point of clarification, what exactly does dropping 4.0 (compared to 4.1) buy us? I'm familiar with the differences between 4 and 5, but less knowledgeable about 4.0 vs. 4.1. As someone who would like to see more logic moved to the database layer, I'm very interested in what shackles we can escape.
Cheers, -Mark
On 11/12/06, Jeremy Epstein <jazepstein@gmail.com> wrote:
Cool! My hosting company (they provide cPanel hosting) finally upgraded to MySQL 4.1 a few weeks ago. I'm guessing that more and more hosting companies are doing the same.
Dropping 4.0 support from Drupal will untie us from many chains and shackles.
Jaza.
On 11/13/06, Karoly Negyesi <karoly@negyesi.net> wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
This will allow us to use more ANSI SQL constructs like subqueries.
Life is beautiful.
Regards
NK
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Out of curiosity, I know we discussed dropping 4.0 support for Drupal 5 a while back on this list, and reasons were given not to. Why the sudden change for Drupal 6, and why was it discussed in IRC instead of on the list?
We discussed dropping 3.23 for D5 and we had an experiment with calc_found_rows and it proved to have no benefit. Hence there is no point in dropping that because there is nothing special 4.0 which we would use. I am not aware of any notion of dropping 4.0 for D5. "Discussion" was I asked Dries whether he is OK with dropping 4.0 for D6 and introducing subqueries. He said yes. That's all. If I bring it to the list then we get at least one very voicy whiner whose provider is still on MySQL 3.22 and can't deal with the fact that life goes on (about 3-4 days ago someone dared to file a critical patch because he found Drupal 5 does not work with his ISP's hacked apart Apache 1.2). Another merry band would not be able to deal with the fact that Drupal needs to run on a wide array of hosts and would demand jumping to 5.1 in the likely event that gets released before Drupal 6. I do not have time for this. Regards NK
On Sunday 12 November 2006 22:40, Karoly Negyesi wrote:
Out of curiosity, I know we discussed dropping 4.0 support for Drupal 5 a while back on this list, and reasons were given not to. Why the sudden change for Drupal 6, and why was it discussed in IRC instead of on the list?
We discussed dropping 3.23 for D5 and we had an experiment with calc_found_rows and it proved to have no benefit. Hence there is no point in dropping that because there is nothing special 4.0 which we would use. I am not aware of any notion of dropping 4.0 for D5.
Nor am I.
"Discussion" was I asked Dries whether he is OK with dropping 4.0 for D6 and introducing subqueries. He said yes. That's all.
If I bring it to the list then we get at least one very voicy whiner whose provider is still on MySQL 3.22 and can't deal with the fact that life goes on (about 3-4 days ago someone dared to file a critical patch because he found Drupal 5 does not work with his ISP's hacked apart Apache 1.2). Another merry band would not be able to deal with the fact that Drupal needs to run on a wide array of hosts and would demand jumping to 5.1 in the likely event that gets released before Drupal 6. I do not have time for this.
I asked a question, sheesh. Chill. :-) All I wanted to know was the reasoning behind the change, since none was provided in the original email. I don't think that's an unreasonable think to ask, given that Drupal 5's MySQL requirements were discussed here on the list. If "by whenever Drupal 6 is released the number of shared hosts running MySQL 4.0 instead of 4.1 should probably be low enough that we can get away with it in return for subqueries" is the answer, then fine; please just say that. (As I've said before, I have no idea what the current deployments are for MySQL 4.0 vs. 4.1.) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
I asked a question, sheesh.
Narrow communication channels. Said question could be read as "hey! you left us out! why?"
Chill. :-) All I wanted to know was the reasoning behind the change, since none was provided in the original email. I don't think that's an unreasonable think to ask, given that Drupal 5's MySQL requirements were discussed here on the list. If "by whenever Drupal 6 is released the number of shared hosts running MySQL 4.0 instead of 4.1 should probably be low enough that we can get away with it in return for subqueries" is the answer, then fine; please just say that. (As I've said before, I have no idea what the current deployments are for MySQL 4.0 vs. 4.1.)
There was a reason provided: free support cycle ended and even 4.1 nears its doom so I can reasonable expect everyone to use at least 4.1 and the need for subqueries are immense. Eventually, I hope we can move to 5.0 and move stuff to stored procedures as it should be, just I do not think it'll be Drupal 6. Small moves :) Regards NK
Anecdote: I have a dirt cheap almost abandoned shared hosting account that I haven't run any live sites on for about 1.5 months. I keep it around for demos, ...etc. I just checked, and they are on MySQL 4.1.21. So, it means even the small hosters have moved (or are moving) to 4.1.
On Monday 13 November 2006 09:06, Khalid B wrote:
Anecdote: I have a dirt cheap almost abandoned shared hosting account that I haven't run any live sites on for about 1.5 months. I keep it around for demos, ...etc.
I just checked, and they are on MySQL 4.1.21.
So, it means even the small hosters have moved (or are moving) to 4.1.
Hmph. One more reason to hate the web host we have at work. They're still 4.0. If they don't switch by next year, I may have to recommend we finally drop them. (Boss likes them, I never have.) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
I have a little question: Why not include MySQL 4.0 support since Drupal 5.x version? Why wait for 6.x release? Cheers and waiting for answers El lun, 13-11-2006 a las 09:20 -0600, Larry Garfield escribió:
On Monday 13 November 2006 09:06, Khalid B wrote:
Anecdote: I have a dirt cheap almost abandoned shared hosting account that I haven't run any live sites on for about 1.5 months. I keep it around for demos, ...etc.
I just checked, and they are on MySQL 4.1.21.
So, it means even the small hosters have moved (or are moving) to 4.1.
Hmph. One more reason to hate the web host we have at work. They're still 4.0. If they don't switch by next year, I may have to recommend we finally drop them. (Boss likes them, I never have.)
-- ReynierPM - Ubuntu Dapper 6.06 5to Ing Informática Aprendiz de mucho, maestro de poco
On 11/13/06, ReynierPM <rperezm@estudiantes.uci.cu> wrote:
I have a little question: Why not include MySQL 4.0 support since Drupal 5.x version? Why wait for 6.x release?
Drupal 5.0 already supports MySQL 4.0, 4.1, and 5.0. We are not waiting till 6.0 to add support. We are trying to drop support for 4.0 in Drupal 6.0.
Good point, I don't follow the topic from the start. I have another little question, when Drupal 5.x will be released? Cheers El lun, 13-11-2006 a las 11:20 -0500, Khalid B escribió:
On 11/13/06, ReynierPM <rperezm@estudiantes.uci.cu> wrote:
I have a little question: Why not include MySQL 4.0 support since Drupal 5.x version? Why wait for 6.x release?
Drupal 5.0 already supports MySQL 4.0, 4.1, and 5.0. We are not waiting till 6.0 to add support. We are trying to drop support for 4.0 in Drupal 6.0. -- ReynierPM - Ubuntu Dapper 6.06 5to Ing Informática Aprendiz de mucho, maestro de poco
ReynierPM wrote:
Good point, I don't follow the topic from the start. I have another little question, when Drupal 5.x will be released?
Haha! Maybe you can read the news yourself: http://drupal.org/drupal-5.0-beta1 Especially the section "So when does 5.0 get released?" Gabor
On 13 Nov 2006, at 08:42, Larry Garfield wrote:
"Discussion" was I asked Dries whether he is OK with dropping 4.0 for D6 and introducing subqueries. He said yes. That's all.
I asked a question, sheesh. Chill. :-) All I wanted to know was the reasoning behind the change, since none was provided in the original email. I don't think that's an unreasonable think to ask, given that Drupal 5's MySQL requirements were discussed here on the list. If "by whenever Drupal 6 is released the number of shared hosts running MySQL 4.0 instead of 4.1 should probably be low enough that we can get away with it in return for subqueries" is the answer, then fine; please just say that. (As I've said before, I have no idea what the current deployments are for MySQL 4.0 vs. 4.1.)
The rule is actually pretty simple: we follow MySQL's official support cycle. When MySQL drops support (and security updates!) for a specific MySQL version, we drop that version as well. When your hosting company is not willing to upgrade, just tell them they are running an insecure MySQL version (unless they have a support contract with MySQL). I'd say this makes for a simple rule of thumb, that requires very little discussion. Hence the prompt decision. :) -- Dries Buytaert :: http://www.buytaert.net/
The rule is actually pretty simple: we follow MySQL's official support cycle.
In a somewhat relaxed fashion -- MySQL 4.0 is not supported since October 1. However, it would have been too hasty to jump to MySQL 4.1 , let there be a transition period. By the time we ship Drupal 6 , MySQL support will end too (it ends on 2006 dec 31th) so it's safe to say that we require _at least_ 4.1 And I need to contradict with Dries on his previous letter: there is extremely little chance D6 will run on M4.0 as the point of all this is to use M4.1 only features. Regards NK
On 14 Nov 2006, at 16:47, Karoly Negyesi wrote:
And I need to contradict with Dries on his previous letter: there is extremely little chance D6 will run on M4.0 as the point of all this is to use M4.1 only features.
Sure, but it remains to be seen if people are actually going to take advantage of them. (I predict they will, but it might be limited to a handful of queries.) -- Dries Buytaert :: http://www.buytaert.net/
On Tuesday 14 November 2006 01:29, Dries Buytaert wrote:
The rule is actually pretty simple: we follow MySQL's official support cycle. When MySQL drops support (and security updates!) for a specific MySQL version, we drop that version as well. When your hosting company is not willing to upgrade, just tell them they are running an insecure MySQL version (unless they have a support contract with MySQL). I'd say this makes for a simple rule of thumb, that requires very little discussion. Hence the prompt decision. :)
A rule of thumb that makes good sense when presented that way, thank you. :-) Perhaps that should be added to a handbook page somewhere? -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
As a point of clarification, what exactly does dropping 4.0 (compared to 4.1) buy us? I'm familiar with the differences between 4 and 5, but less knowledgeable about 4.0 vs. 4.1. As someone who would like to see more logic moved to the database layer, I'm very interested in what shackles we can escape.
http://dev.mysql.com/doc/refman/4.1/en/news-4-1-x.html Subqueries and derived tables (unnamed views). INSERT ... ON DUPLICATE KEY UPDATE ... syntax. Note that this does note exist in postgresql but if we decide we need this then a CREATE RULE ... ON INSERT ... INSTEAD might or might not help (needs to be done per table if I understand this). Later :) GROUP_CONCAT Again, not standard and the only solution for pgsql I know requires plpgsql Extensive Unicode (UTF8) support. Goba already praised this This is pretty much about it, I would really like to use GROUP_CONCAT but this needs to be discussed further (for Oracle folks, http://tkyte.blogspot.com/2006/08/evolution.html ) Regards NK
Just to record my research.
GROUP_CONCAT Again, not standard and the only solution for pgsql I know requires plpgsql
a) sammys has no probs with plpgsql b) while many routines require plpgsql from http://pgfoundry.org/projects/mysqlcompat/ but group_concat does not. Yay. So, in case we need it, I think it's good to go, I provided Oracle and pgsql implementations -- but again, this will need further discussion when there will be an issue that's best solved with GROUP_CONCAT. Regards NK
On 13.11-05:59, Karoly Negyesi wrote: [ ... ]
GROUP_CONCAT Again, not standard and the only solution for pgsql I know requires plpgsql [ ... ] So, in case we need it, I think it's good to go, I provided Oracle and pgsql implementations -- but again, this will need further discussion when there will be an issue that's best solved with GROUP_CONCAT.
http://db4free.blogspot.com/2006/01/hail-to-groupconcat.html note, the response for postgresql. -- : fergus cameron : -cameron------------- : : ^^^^^^@cameron-consulting.ie : ----------consulting- :
On 12-Nov-06, at 3:38 PM, Karoly Negyesi wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
I did a survey of some random hosts I found mentioned in the "2006 hosting providers evaluations" thread: http://drupal.org/node/46707 and the hosting forum. - Dreamhost: 5.0 or 4.1 for older plans (http://wiki.dreamhost.com/ index.php/MySQL) - GoDaddy: 4.0.24 (http://help.godaddy.com/article.php?article_id=221) - 1and1: "4" (http://faq.1and1.com/scripting_languages_supported/ mysql_database/1.html) - anyone can confirm this? - NearlyFreeSpeech.net: 4.1.x (https://www.nearlyfreespeech.net/) - props for not making me have to hunt around for this info! - Netfirms: 4.1 (http://www.netfirms.com/web-hosting-advantage- compare/zone/advantage) - Total Choice Hosting: 4.0.12 (http://www.totalchoicehosting.com/ help/faqs.html) - Servage.net: "v4 & v5" (http://www.servage.net/page/hosting_features/) - Media Temple: 4.1.11 (http://www.mediatemple.net/webhosting/gs/) - Site5: "MySQL 4+" (http://www.site5.com/hosting/) -- could someone confirm which version they run? - AllCheapWeb.com - 4.0.24 (http://help.securepaynet.net/article.php? article_id=221&topic_id=67&prog_id=allcheapweb&) - Siteground: 4.1.21 (http://www.siteground.com/hosting_features.htm) - TextDrive: 4.1 (http://textdrive.com/hosting/shared) So of that list of 12, 3 are still using 4.0.x, and a couple more are ambiguous. Just some data that might or might not be worth factoring into this decision. -Angie
On 11/13/06, Angela Byron <drupal-devel@webchick.net> wrote:
I did a survey of some random hosts I found mentioned in the "2006 hosting providers evaluations" thread: http://drupal.org/node/46707 and the hosting forum.
Great idea! Thanks for summarizing these.
- Site5: "MySQL 4+" (http://www.site5.com/hosting/) -- could someone confirm which version they run?
On one account I know (not necessarily representative) it is using 4.1. Regards, Greg
-- Larry Garfield On Mon, November 13, 2006 10:01 am, Angela Byron said:
On 12-Nov-06, at 3:38 PM, Karoly Negyesi wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
I did a survey of some random hosts I found mentioned in the "2006 hosting providers evaluations" thread: http://drupal.org/node/46707 and the hosting forum.
- Dreamhost: 5.0 or 4.1 for older plans (http://wiki.dreamhost.com/ index.php/MySQL) - GoDaddy: 4.0.24 (http://help.godaddy.com/article.php?article_id=221) - 1and1: "4" (http://faq.1and1.com/scripting_languages_supported/ mysql_database/1.html) - anyone can confirm this? - NearlyFreeSpeech.net: 4.1.x (https://www.nearlyfreespeech.net/) - props for not making me have to hunt around for this info! - Netfirms: 4.1 (http://www.netfirms.com/web-hosting-advantage- compare/zone/advantage) - Total Choice Hosting: 4.0.12 (http://www.totalchoicehosting.com/ help/faqs.html) - Servage.net: "v4 & v5" (http://www.servage.net/page/hosting_features/) - Media Temple: 4.1.11 (http://www.mediatemple.net/webhosting/gs/) - Site5: "MySQL 4+" (http://www.site5.com/hosting/) -- could someone confirm which version they run? - AllCheapWeb.com - 4.0.24 (http://help.securepaynet.net/article.php? article_id=221&topic_id=67&prog_id=allcheapweb&) - Siteground: 4.1.21 (http://www.siteground.com/hosting_features.htm) - TextDrive: 4.1 (http://textdrive.com/hosting/shared)
So of that list of 12, 3 are still using 4.0.x, and a couple more are ambiguous.
Just some data that might or might not be worth factoring into this decision.
-Angie
I can add two to that list: Pair Networks: 4.1 (http://www.pair.com/) FutureQuest: 4.0 (http://www.futurequest.net/) --Larry Garfield
What about PHP5? Is the same migration? I mean wich host of this migrate from PHP4.x to PHP5.x version? Cheers El lun, 13-11-2006 a las 11:01 -0500, Angela Byron escribió:
On 12-Nov-06, at 3:38 PM, Karoly Negyesi wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
I did a survey of some random hosts I found mentioned in the "2006 hosting providers evaluations" thread: http://drupal.org/node/46707 and the hosting forum.
- Dreamhost: 5.0 or 4.1 for older plans (http://wiki.dreamhost.com/ index.php/MySQL) - GoDaddy: 4.0.24 (http://help.godaddy.com/article.php?article_id=221) - 1and1: "4" (http://faq.1and1.com/scripting_languages_supported/ mysql_database/1.html) - anyone can confirm this? - NearlyFreeSpeech.net: 4.1.x (https://www.nearlyfreespeech.net/) - props for not making me have to hunt around for this info! - Netfirms: 4.1 (http://www.netfirms.com/web-hosting-advantage- compare/zone/advantage) - Total Choice Hosting: 4.0.12 (http://www.totalchoicehosting.com/ help/faqs.html) - Servage.net: "v4 & v5" (http://www.servage.net/page/hosting_features/) - Media Temple: 4.1.11 (http://www.mediatemple.net/webhosting/gs/) - Site5: "MySQL 4+" (http://www.site5.com/hosting/) -- could someone confirm which version they run? - AllCheapWeb.com - 4.0.24 (http://help.securepaynet.net/article.php? article_id=221&topic_id=67&prog_id=allcheapweb&) - Siteground: 4.1.21 (http://www.siteground.com/hosting_features.htm) - TextDrive: 4.1 (http://textdrive.com/hosting/shared)
So of that list of 12, 3 are still using 4.0.x, and a couple more are ambiguous.
Just some data that might or might not be worth factoring into this decision.
-Angie
-- ReynierPM - Ubuntu Dapper 6.06 5to Ing Informática Aprendiz de mucho, maestro de poco
Reynier We are discussing one thing in this thread: dropping MySQL 4.0 for Drupal 6.0. We are not discussing when Drupal 5.0 will be out nor which PHP version are supported. You can start a new topic for that, and do what Angela did, checking the web sites of providers and posting a list. On 11/13/06, ReynierPM <rperezm@estudiantes.uci.cu> wrote:
What about PHP5? Is the same migration? I mean wich host of this migrate from PHP4.x to PHP5.x version? Cheers El lun, 13-11-2006 a las 11:01 -0500, Angela Byron escribió:
On 12-Nov-06, at 3:38 PM, Karoly Negyesi wrote:
Hi,
After a little chat with Dries on #drupal :
The plan is to drop MySQL 4.0 support in Drupal 6.0 (note that free support already ended for this version of MySQL).
I did a survey of some random hosts I found mentioned in the "2006 hosting providers evaluations" thread: http://drupal.org/node/46707 and the hosting forum.
- Dreamhost: 5.0 or 4.1 for older plans (http://wiki.dreamhost.com/ index.php/MySQL) - GoDaddy: 4.0.24 (http://help.godaddy.com/article.php?article_id=221) - 1and1: "4" (http://faq.1and1.com/scripting_languages_supported/ mysql_database/1.html) - anyone can confirm this? - NearlyFreeSpeech.net: 4.1.x (https://www.nearlyfreespeech.net/) - props for not making me have to hunt around for this info! - Netfirms: 4.1 (http://www.netfirms.com/web-hosting-advantage- compare/zone/advantage) - Total Choice Hosting: 4.0.12 (http://www.totalchoicehosting.com/ help/faqs.html) - Servage.net: "v4 & v5" (http://www.servage.net/page/hosting_features/) - Media Temple: 4.1.11 (http://www.mediatemple.net/webhosting/gs/) - Site5: "MySQL 4+" (http://www.site5.com/hosting/) -- could someone confirm which version they run? - AllCheapWeb.com - 4.0.24 (http://help.securepaynet.net/article.php? article_id=221&topic_id=67&prog_id=allcheapweb&) - Siteground: 4.1.21 (http://www.siteground.com/hosting_features.htm) - TextDrive: 4.1 (http://textdrive.com/hosting/shared)
So of that list of 12, 3 are still using 4.0.x, and a couple more are ambiguous.
Just some data that might or might not be worth factoring into this decision.
-Angie
-- ReynierPM - Ubuntu Dapper 6.06 5to Ing Informática Aprendiz de mucho, maestro de poco
Angela Byron wrote:
- 1and1: "4" (http://faq.1and1.com/scripting_languages_supported/mysql_database/1.html) - anyone can confirm this? My 1&1 system returns 4.0.25 for the client, 4.0.27 for the server (two different machines).
Gary
It's pointless making a census now, D6 will be released half a year from now. MySQL Database Server GA Date Active Support Ends Extended Support Ends 4.0 2003-03-15 2006-09-30 2008-12-31 4.1 2004-10-23 2006-12-31 2009-12-31 so there. It might be that many providers will skip 4.1 -- fine with me.
On 11/13/06, Angela Byron <drupal-devel@webchick.net> wrote:
I did a survey of some random hosts I found mentioned in the "2006 hosting providers evaluations" thread: http://drupal.org/node/46707 and the hosting forum. [snip]
Anecdote: my hosting provider, Verve Hosting http://www.vervehosting.com/shared.html runs 4.0.27-standard on the server my sites are hosted on, but they announced they're upgrading all of their servers to 4.1.20. -- Richard Eriksson http://bryght.com/
On 13 Nov 2006, at 21:19, Richard Eriksson wrote:
Anecdote: my hosting provider, Verve Hosting http://www.vervehosting.com/shared.html runs 4.0.27-standard on the server my sites are hosted on, but they announced they're upgrading all of their servers to 4.1.20.
The reason that many hosting companies have yet to upgrade, is because the upgrade from MySQL 4.0 to MySQL 4.1 is quite a pain. It's much easier to upgrade from 4.1 to 5.0, for example. (Sounds familiar? ;)) If you're worried about getting stuck with an unsupported MySQL version, I'd suggest that you send your hosting providing an e-mail. Ask them for their upgrade strategy/plans, and point them to the MySQL documentation if necessary. The fact that we drop support for MySQL 4.0 does not necessarily mean that Drupal 6.0 will stop working on MySQL 4.0. Chances are we happen to be backward compatible. -- Dries Buytaert :: http://www.buytaert.net/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dries Buytaert wrote:
Chances are we happen to be backward compatible.
Then why drop support for 4.0 at all? Subqueries (and stored procedures if 4.1 is skipped) allow optimizations, that are not possible in 4.0. IMO these chances are lost when coding for compatibility. Furthermore: The core might be compatible, some contributed modules might not be. The moment that drupal does not officially support 4.0 anymore, module developers will use 4.1 features for their modules. The effect will be that module developers will have to tell their users which database version to use, because some users still have 4.0 installed and only notice the missing requirements when they install such a module. Greetings, - -- Oswald Jaskolla Ingenieurbüro Richard Schieferdecker Kreuzherrenstraße 2, 52062 Aachen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFWbWVuinSHQ/4/T4RAnSFAJ9gSuGwA0Quqg/pt1M8LuQvajNtJQCfRuFy CIH5/aN+qNuk55aVHl+430g= =YlS3 -----END PGP SIGNATURE-----
participants (15)
-
Angela Byron -
Dries Buytaert -
Gabor Hojtsy -
Gary Feldman -
Greg Knaddison - GVS -
Jeremy Epstein -
Karoly Negyesi -
Khalid B -
Larry Garfield -
Mark Fredrickson -
Oswald Jaskolla -
ReynierPM -
Richard Eriksson -
Steve Dondley -
ttw+drupal＠cobbled.net