I know that.. I am not developing a new system but adding a new module to an existing
application which is based on 4.1. And as I said earlier.. its not only me who can take
decision of upgrading... otherwise I would prefer to upgrade instead of seeking a
solution that isnt really a solution..
Personally I'm always ready to learn, although I do not always like being taught
From: Joerg Bruehe <Joerg.Bruehe@stripped>
Cc: Mysql <mysql@stripped>
Sent: Thu, 5 November, 2009 11:39:11 PM
Subject: Re: Fw: 50M records each year.. how to handle
> > What forbids you to upgrade to a newer version right now?
> Because I am not the person who take this decision.. I can suggest but its not in my
hand to decide.. I understand that Its taking more time thn what It would take to
upgrade.. But this is how things work..
MySQL version 4.1 is past its "end-of-life", you will not get any
updates and bug fixes for it, whatever the severity of the issue may be
(including security bugs).
Your question sounded like you are introducing some new application.
Doing this on a base whose service life has expired is not just silly,
it is plain wrong and would (if any problems arise) be considered
I don't know what your local legal rules are, but in several parts of
the world a company doing this would put themselves at great risks.
I can only advise you (and your decision powers) *extremely* stongly to
use a version which is released for production purposes and in active
Currently, this would be MySQL 5.0 and 5.1, but 5.0 will also soon reach
its end-of-life, so the next upgrade would be imminent.
You (and your decision makers) should do the right thing for your
organization and start this using 5.1!
Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@stripped
(+49 30) 417 01 487
Sun Microsystems GmbH, Komturstraße 18a, D-12099 Berlin
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.