Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I actually used your module on with mysql 5.0.51a and with this version your module works fine. I installed it via sql. Instead of blocking of installation with your module. It would be nice if there was a settings where you would ignore the requirement of mysql 5.1, if your have testede with a different version and it still works. Could be a simple setting or something else. I think the sql joins issue that was on the ticket in mysql has been ported to 5.0 version of mysql.
- Ying
Comment | File | Size | Author |
---|---|---|---|
#7 | 924072-rnr-UNSUPPORTED-MySQL-pre-5.1.patch | 464 bytes | AaronBauman |
Comments
Comment #1
yingtho CreditAttribution: yingtho commentedComment #2
markus_petrux CreditAttribution: markus_petrux commentedAs far as I can tell, this feature is not officially supported until MySQL 5.1. See the bug report I posted in the project page of this module. Here's the link for reference too:
http://bugs.mysql.com/bug.php?id=1591
So... I'm afraid openning the door to support older versions of MySQL is not a good idea. If it works for you, good, but I would always suggest you to upgrade to a newer version of MySQL.
Comment #3
dorien CreditAttribution: dorien commentedI have the same problem. Don't think I can ask for an upgrade of the university server :-/
Will do a short test to see if it might join correctly on 5.0.18
Comment #4
liquidcms CreditAttribution: liquidcms commentedi have 5.1 on my local devel.. which is where db was originally built.. and then moved it to my server without even realizing there was an issue with this module and mysql rev.. server uses 5.0.91 - and my site works fine.
so what is the real issue? obviously not unsupported syntax prior to 5.1. is it perhaps just worse performance? in which case code shouldn't limit its use - or maybe syntax was supported pre-5.1 at some rev of 5.0? i am trying to check the bug report to see if mentioned there.. but mysql bug site is down.
Comment #5
ptaff CreditAttribution: ptaff commentedI confirm that under CentOS' MySQL-5.0.77-4.el5_4.2, the MySQL bug #1591 is fixed, the included test case gives the right results. I don't know if the fix is a custom backport from CentOS or if the fix was backported in MySQL's main tree somewhere in a 5.0.x release.
Comment #6
markus_petrux CreditAttribution: markus_petrux commentedAFAICT, the official source related to this feature is that bug report (see #2 above). MySQL 5.0.x had a bug that was fixed in 5.1.
CentOS re-uses the Red Hat repos. Maybe there's a way to check what they did here. Still, to change the code in this module, we would need a method to check compatibility that is 100% reliable in all possible platforms.
Also, you may want to check MySQL lifecycle policy:
http://www.mysql.com/about/legal/lifecycle/
Active support for MySQL 5.0 ended a year ago. Extended support ends next year, end of 2011.
Comment #7
AaronBaumanHere's an unsupported patch for anyone stuck on shared hosting.
=]
Comment #8
ikeigenwijs CreditAttribution: ikeigenwijs commentedYour MySQL Server is too old (5.0.51a). The Reverse Node Reference module requires at least MySQL 5.1
also shared hosting university
Comment #9
Jon Nunan CreditAttribution: Jon Nunan commentedI'm running 5.0.45-community-nt on Windows and the bug doesn't appear to be present.
I think this bug got fixed in 5.0.12, see the first entry in the changelog: http://dev.mysql.com/doc/refman/5.0/en/news-5-0-12.html
Comment #10
redhoodie CreditAttribution: redhoodie commentedThis also worked for me on;
mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2
(Debian GNU/Linux 4.0)