I have a website that I might move to the Open Source Joomla Content Management style of website. It uses one MySQL database to store everything.
I rent a server in cyberspace that has CPanel as the resource manager, controlling such things as installing MySQL and other software into the (redhat) rented Linux/Apache server.
I’ve tested Joomla on the rented site – it’s worth pursuing. I’d like to install Joomla and MySQL on my office openSUSE Apache Server and then ftp all the Joomla files and the MySQL database to the server in the sky.
That way I can back it up and retrieve independent any time I like.
The question is: will a MySQL database installed in openSUSE work OK if I just ftp it to a Redhat machine?
PS I’ve never installed or used MySQL (except by clicking a button on the web interface in my rented server – which I want to avoid).
There are differences in capabilities between MySQL versions so you have to watch out for those. By and large, if the version difference is not large, you’ll be ok. E.g. 5.0.x and 5.0.y.
Also you should use the dump from mysqldump to exchange information, not the raw data files. phpMyAdmin can frontend this for you. You can compress the dump to reduce transfer bulk.
I suppose the best way is to make a website with one page (minimum work) on openSUSE and then see if I can transfer it to the rented space in working order. That shouldn’t be more than 1/2 a day’s work.
You should first check the MySQL versions at both ends before wasting 1/2 day.
Just for a quick read: MySQL :: MySQL 5.1 Reference Manual :: 2.12.1 Upgrading MySQL
I am not a MySQL user (in fact, I prefer postgreSQL to MySQL due to various technical reasons), but I have experience with other databases. Databases are quite “notorious” when it comes to upgrade from one version to another (especially when you want to skip one or more versions in between).
Latest versions of MySQL support many of the modern RDBMS features but some of the features are still restricted. I am sure that it will get further improved in the future versions.
I have been using large databases for the last 17 years and it was difficult for me to run anything on non-ACID complaint databases. Also, I always wanted features like Foreign Key support, Views, Stored Procedures, Triggers, Unions, Full Joins, Constraints etc. Lately, MySQL started adding these features but still restrictions are there: For example: An API based application can bypass a table trigger action.
And finally, I am not amused when Sun bought MySQL
I am not against Sun (In fact, I use Sun enterprise servers to run large databases). But, you know Sun is a commercial company. And, with recent acquisition of Sun by Oracle, I don’t know what is going to happen to MySQL.
>
>Latest versions of MySQL support many of the modern RDBMS features but
>some of the features are still restricted. I am sure that it will get
>further improved in the future versions.
>
>I have been using large databases for the last 17 years and it was
>difficult for me to run anything on non-ACID complaint databases. Also,
>I always wanted features like Foreign Key support, Views, Stored
>Procedures, Triggers, Unions, Full Joins, Constraints etc. Lately, MySQL
>started adding these features but still restrictions are there: For
>example: An API based application can bypass a table trigger action.
>
>And finally, I am not amused when Sun bought MySQL
>I am not against Sun (In fact, I use Sun enterprise servers to run
>large databases). But, you know Sun is a commercial company. And, with
>recent acquisition of Sun by Oracle, I don’t know what is going to
>happen to MySQL.
Oracle’s acquisition of Sun did not make much sense before. MySQL,
and associated open source tools, was getting too good. Larry made a
misjudgment here, the open source community will just keep it.
