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