On 7/13/06, Dan Trainor <[EMAIL PROTECTED]> wrote:
Martin Jespersen wrote:
> Dan has a very good point, be mindfull of the changed password
> algorithm, that actually was a bit of a bother to me since i have tons
> of users defined in my grant tables.
>
>
> Dan Buettner wrote:
>> Dan, I wouldn't bother with the intermediate steps (4.0, 4.1) . Waste
>> of time (fine products, but you say you want to go to 5.0). I'd go
>> direct to 5.0, using mysqldump'd data as Martin did. If you're
>> all-MyISAM then it might also work to simply upgrade your binaries and
>> keep your data files, though you'll want to watch for the fix
>> permissions script and also be mindful of the password changes that
>> came about with 4.1.
>>
>> Dan
>>
>>
>> On 7/13/06, Martin Jespersen <[EMAIL PROTECTED]> wrote:
>>> I recently upgraded from 3.23.58 -> 4.1.20 without any hickups.
>>>
>>> I simply dumped my databases with mysqldump on the 3.23.58 installation
>>> and imported them again from inside the mysql client by using the
>>> "source" command.
>>>
>>>
>>>
>>> Dan Trainor wrote:
>>> > Hi -
>>> >
>>> > I know we've rolled this around the list a few times, but I was
>>> > wondering if there's been any real development on the subject
>>> lately. I
>>> > know half of you are saying "Forget it... go with a newer version and
>>> > get over it", and I'd really really like to, but i have a lot of data
>>> > store under 3.23.x.
>>> >
>>> > The documentation says that you must follow 3 -> 4.0 -> 4.1 -> 5.0 ...
>>> > ..., and that's just what I'm about to do.
>>> >
>>> > I guess what I'm looking for here is some advice from people who have
>>> > done it. If there's not an all-in-one silly stupid way to upgrade the
>>> > data in this manner (i.e. with one fell swoop of some handy dandy
>>> > application), would someone on an RPM-based system simply upgrade RPMs
>>> > in sequential order as indicated, and hope that the data follows? Is
>>> > this probably one of the more successful ways of doing this?
>>> >
>>> > I'm still exploring my options, but I think that's what I'm going
>>> to end
>>> > up going with here - one step at a time.
>>> >
>>> > If you guys wouldn't mind terribly talking about this for a few more
>>> > posts, I (and hopefully others) would greatly appreciate it.
>>> >
>>> > Thanks for the time
>>> > -dant
>>> >
>>>
>>> --
>>> MySQL General Mailing List
>>> For list archives: http://lists.mysql.com/mysql
>>> To unsubscribe:
>>> http://lists.mysql.com/[EMAIL PROTECTED]
>>>
>>>
>>
>
Hi -
Thanks, both of you, for your replies.
Like I said, I've experienced problems in the past with a mysqldump
between major version changes. Maybe it's just my luck, or maybe it's a
hit-or-miss from big jumps, I'm not entirely sure.
So did I. I recommend (always) to follow the devs advice at the docs,
to migrate to each major version, check everything and go on. There
were MAJOR changes, password, grant table, new fields, old fields
renamed, specially at the mysql database. Its not THAT hard, and
instead of a waste of time, it may be gain of time as you may
encounter serious errors when going directly to 5 from 3.
No matter what others say, I had a pretty good fight with grant table,
users, permissions, passwords and some data lost in fields in a
migration directly, wich was easily fixed with scripts provided by
mysql specially for each major version change.
Right now, most of my data is InnoDB. As I believe Martin pointed out
(or maybe not... someone from [EMAIL PROTECTED]), be wary of transactions,
which I can overwrite using an import switch.
I was able to actually convert to 5.0.22 directly from 3.23.58, and I'm
having my devs mow through the data to see if it all works as designed.
They are having trouble with passwords, but they're fixing that on a
case-by-case basis, which is fine with us.
I'll keep you guys posted regardless. It seems that this subject pops
up a lot with conflicting answers, so I'd like to give everyone else as
much information about the process as I can.
Thanks again, much appreciated.
-dant
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
