RE: [MLUG] RHEL and MySQL packages revisited

["Woodsmall, Ryan \(IATS\)" <EMAIL:PROTECTED>]

Forgot to address your other questions.
 
Downtime was negligible since I built on a development server before it went live.  Can't help you here.
 
Backwards compatibility is fine; we've experienced no problems whatsoever.  MySQL 3-based scripts still work fine.  Everything *should* work flawlessly as long as you're using a higher-level layer (PHP's built-in MySQL support, Perl's DBI/DBD, etc.) to abstract the work.  C and C++ clients should work fine as long as you have the compat libraries installed.
 
You might have to tinker around in my.cnf after you update to MySQL 4.  It's a good bet you will.  We generally start out with the medium-level config and go from there.
 
Nothing *should* break.  Again, we've had zero problems.  We even updated a 3.0 machine to 4.0 Max, then updated that 4.0 machine to 4.1, then rebuilt the RPMs I mentioned in my previous message against the new devel RPMs and It Just Worked (R)(TM)(C).  There are some issues with the 4.0 -> 4.1 table migration, but it's nothing a little brute force can't fix; 3.0 -> 4.0 table migration is 99.9% flawless in my experience.  Most of the DB-based apps we use have upgrade scripts that will do the heavy-lifting for you if you choose to go with 4.1, so all you have to do is dump data-filler statements instead of DB and table creation statements, then the data.
 
MySQL 4.1 is super-nice so far, fixing some weirdness with 4.0 and making the whole shebag more standards-compliant.  Hopefully, 5.0 should be the positive answer to the "Yes, but is it enterprise-quality?" question that undoubtedly pops up.
 
As long as they keep it fast, simple AND right, that is...
 
  ryan woodsmall
    EMAIL:PROTECTED <mailto:EMAIL:PROTECTED> 

 
________________________________

From: EMAIL:PROTECTED on behalf of Matthew Schmidt
Sent: Sat 12/4/2004 2:52 PM
To: EMAIL:PROTECTED
Subject: [MLUG] RHEL and MySQL packages revisited



Hi Folks,

Let me rephrase my question:

Is anyone out there running RHEL with a version of MySQL that is not
officially supported by RedHat?

We've developed a kick a$$ application that depends on MySQL 4.X. Our
servers run something like 3.2.

I'm not a personal fan of RedHat, but it is all that is supported by
our IT folks. They do not want to install any MySQL packages that are
not the official RHEL RPMs. I would like to gather some experiential
data from folks who have installed unsupported MySQL RPMs on their
RedHat systems (I suppose Fedora systems, too).

How did the install go? Do you remember your downtime? How was
backward compatibility? Did you have to tinker around or did things
"automagically" work? Did any PHP scripts break? Don't you love the
union statement in MySQL 4.X?

I yearn for the day when people start to grok that Linux != RedHat.

Thanks again!

Matt

<<winmail.dat>>

_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members