On Jan 20, 2006, at 4:30 PM, Eric Dannewitz wrote:
> Thanks to Blake for the script about the email bounces!
I second that :)
> Another question. I potentially have to rebuilt my server that my
> slash sites run on. I'm wonder what the best way to move the MySQL
> database is. The server is currently running FreeBSD 4.11 with
> MySQL 4.1.14. I'm thinking of running FreeBSD 5.3 with MySQL 5.
> Should a dump of the database be just fine to get the slash stuff
> moved over?
The data? One would think so. However, did you read the changelog of
"what's changed" documentation on MySQL's website for migrating from
v4 to v5? If not, you should. That would give you a lot of insight.
And heck, you can always put mysql5 on another box, or the same box
(not running w/ tcpip access in a different location on the file
system) and try a db create and db import of the data from your slash
I'd guess it'd work. However, I haven't read any of the MySQL 5 docs
> Is there any advantage to running Mysql 5 over 4.1? Any thing I
> should watch out for?
I'm sure there are! However, again, did you read the mysql v5 info?
http://www.mysql.com/ . Off the top of my head, it's got stored
procedures, triggers and views. No full-text-query with innodb, but I
recall read somewhere that's coming eventually.
> Thanks in advance.
From what I've heard mention, someone from the OSTG group has been
cleaning things up in the slashcode source (cvs version) to work with
When will it be done? I don't know, never been told - but I would
guess "when it's done", sometime this winter/spring.
So - If I were you, I'd grab the latest-stable MySQL 4.1x, install it
and use it, for now, if it's a production site that's gotta be
stable. If you're "just testing" then install v5 and give it a test
runthrough and be sure to email the slashcode-dev list so everyone
can hear how it went :)