My shared hosting company switched our database access from MySQL 4 to 5. Do I need to upgrade or do anything to the database folder that comes with the drupal installation. Right now it has scripts database 4.0 MySQL, database 4.1 MySQL, database pgsql, and the update.inc script. Do I need a 5.0 MySQL script.

Also I am still on 4.7 version of Drupal cause the shared hosting company that I have do not want to upgrade their version of drupal to 5. Now I understand that I cannot upgrade to 5 myself cause I am with a cheap shared hosting plan. If I had a dedicated server then I can upgrade. So mainly I'm asking is there anyway to upgrade while being with a cheap hosting company. They updated everything else like MySQL 4 to 5 but not Drupal. :- (

Thanx. JayDigga ;-)

Comments

vm’s picture

Your host is not responsible for upgrading Drupal to 5.x, you are. Your site as is should work fine on MySQL5 regardless of files in the icnludes folder. The DB was prepared during installation.

I assume, the site is working fine correct ?
___________________________________________________________________________________________________
The search tool on Drupal.org really does work. This message has been brought to you by the letter X. Thanks for watching! : )

jaydigga’s picture

Thanx for answering the database question. My fault though about the upgrading question. I probably typed my question the wrong way. I know they are not responsible for upgrading to 5.x. I would love to do it myself. I think being with a shared hosting company won't let me. I was told though by others that you cannot upgrade your version of Drupal if you started off installing 4.7 from the shared hosting company's page of available CMSs to install from their control panel. I tried to upload and install Drupal myself the first time but had database connection issues. Called the company and they said you can only install the drupal they have. They said since you do not have full access to the MySQL database on the server which you need to install or update drupal yourself, you cannot just upgrade Drupal. Overall, I guess my question is; Do I need to have a dedicated server if I want to upgrade and install other versions of Drupal? I feel with shared hosting you are limited which is why it's so cheap. I know the majority of all the users with Drupal have dedicated servers.

Do what you enjoy and love. JayDigga ; - )

jtjones23’s picture

You don't need a dedicated server, you need a new hosting company. Do a search on what others are using to host their Drupal sites. And cheaper is rarely better.

vm’s picture

if you don't learn how to do it on your own, you will wind up in a world of hurt. As you fall further and further behind on security updates and upgrades you are that much more vulnerable to your site being taken down by the exploits that have been and will be patched.
___________________________________________________________________________________________________
The search tool on Drupal.org really does work. This message has been brought to you by the letter X. Thanks for watching! : )

cog.rusty’s picture

Most Drupal users use shared hosting, not dedicated servers, and they can upgrade, no problem. There are $5 plans which are perfectly OK.

What your host probably meant was that it's not their business to help you upgrade in any way, besides the automatic install script they have.

In short, you only need to move out the old Drupal files and upload the new version (using an FTP program), enter the database settings ($db_url and $db_prefix) from your old settings.php file to the new one, run update.php, and that is all.

Matters would be more complicated if you have any additional modules installed, but I guess their automatic installer has only installed core Drupal, so things should be simple.

Alternatively, you may prefer to upload a new Drupal version in a subdirectory to experiment. If your host's cpanel allows, you can create a new database for the second site. If not, you can use the same database as the first site, but with a different prefix for its table names (for example "site2_users" instead of "users")