MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Ugo Bellavance Date:November 18 2004 8:22pm
Subject:Re: 4.1.7 serious problems
View as plain text  
Sasha Pachev wrote:
> 
>>>
>>> It can be even simpler than that, if you stay withing the same 
>>> branch. Just replace mysqld and share/english/errmsg.sys ( or 
>>> share/<your langauge>/errmsg.sys if you want them in your native 
>>> language) with the files from the new version.
>>
>>
>>
>> This is for the source, binary or both?  Sorry to ask stupid 
>> questions, but I do have read 3 MySQL books (including yours), and 
>> went through the manual, and I've never really seen a section about 
>> updating MySQL.
> 
> 
> It does not matter. mysqld is the only file in the server that really 
> does the job - mysqld_safe is just a wrapper and if it does change from 
> version to version at all, using the old version does not hurt. mysqld 
> does need to see the error messages file on startup and the error 
> messages file gets changed sometimes from version to version. mysqld 
> does know how many error messages it is supposed to have, and will not 
> start unless the error messages file has the expected number. Otherwise, 
> if you are within the same version, mysqld will be able to deal with all 
> the files from the old one.

So all I have to do, using the binary, is to take the mysqld file and 
replace my old one (from 4.1.3 to 4.1.7, for example).

And for the source, I compile in another directory, then take the mysqld 
file and replace my old one?

Is that documented somewhere?

> 
>>
>>
>> Hmmm, ok.  Do you think I should file a bug?
> 
> 
> Lenz is already looking at it.
> 

Thanks.

Thread
4.1.7 serious problemsUgo Bellavance4 Nov
  • Re: 4.1.7 serious problemsAnders Green4 Nov
    • Re: 4.1.7 serious problemsUgo Bellavance5 Nov
  • Re: 4.1.7 serious problemsGleb Paharenko5 Nov
    • Re: 4.1.7 serious problemsUgo Bellavance5 Nov
Re: 4.1.7 serious problemsHeikki Tuuri6 Nov
  • RE: 4.1.7 serious problemsDonny Simonton6 Nov
  • Re: 4.1.7 serious problemsUgo Bellavance8 Nov
    • Re: 4.1.7 serious problemsSasha Pachev11 Nov
      • Re: 4.1.7 serious problemsUgo Bellavance11 Nov
        • Re: 4.1.7 serious problemsSasha Pachev12 Nov
          • Re: 4.1.7 serious problemsUgo Bellavance12 Nov
            • Re: 4.1.7 serious problemsSasha Pachev13 Nov
              • Re: 4.1.7 serious problemsUgo Bellavance13 Nov
                • Re: 4.1.7 serious problemsSasha Pachev18 Nov
                  • Re: 4.1.7 serious problemsUgo Bellavance18 Nov
                    • Re: 4.1.7 serious problemsSasha Pachev18 Nov
                      • Re: 4.1.7 serious problemsUgo Bellavance19 Nov