henry0
msg:1580113 | 12:07 pm on Oct 15, 2005 (gmt 0) |
Thanks Mack good finding This leads me to the following question: How does one perform seamlessly an upgrade?
Do a dump and a full reload which does not make sense
for current operations are to be stopped. Or the best way which should be? Obviously I never yet perform a "Live" upgrade on a server
since I use mostly managed server.
but for experiment purposes I am considering fully dedicted server.
|
txbakers
msg:1580114 | 12:39 pm on Oct 15, 2005 (gmt 0) |
I haven't investigated it yet, but I think a dump/reload is going to be the only way. When I was using all myISAM tables it was easy just to copy the data directory from one server to the other. With the innoDB tables it hasn't worked as well to build new schemas or backup dbs.
|
mack
msg:1580115 | 2:04 pm on Oct 15, 2005 (gmt 0) |
In terms of exprting date to the new version, does anyone know what major differences there are that may pose problems? Mack.
|
coopster
msg:1580116 | 12:40 am on Oct 17, 2005 (gmt 0) |
On one of my text boxes it was as easy as using the same data directory, no dumping/restoring, no conversions. Note, the particular box did not include any InnoDB tables so I cannot offer any experience there ... yet.
|
txbakers
msg:1580117 | 12:58 am on Oct 25, 2005 (gmt 0) |
I've installed 5 and it looks very good so far. But I'm still faced with the backup/restore issue. If I use the SQL based backup the text files are too huge to restore! At least through the mySQL gui tools. Maybe a command line would be better.
|
|
