importing

Bug: Can't import databases with "CREATE" in them

Hey, folks. I encountered an error while importing a database with a CREATE statement, e.g.:

CREATE DATABASE `mydatabase` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

It worked fine when I commented out that line. It would be wise to make DAMP ignore CREATE DATABASE statements.

Sorry if this has been reported already. Good luck!

--Tom

Import content - relationships troubles between content types

Hi,

After too many hours spent on google without results, I’m asking your help.

I’m developing a website in drupal and I’m stuck with a relationship’s problem between two content types.

I’ve got my first content type: Country, with many fields and especially one containing the ISO3166 code of the country (unique).

I’ve got my second content type: Region (or country’s subdivision or whatever), with two fields, one containing the region’s name and the other containing the ISO3166 code of the country it belongs. Read full article »

db Naming and Importing Problem

In trying to set up my Acquia Drupal installation on a hosting service, I have set up an empty db using the service's control panel. I then uploaded a backup db from my local computer, which I had created using my local phpMyAdmin's Export command.

The local localhost site was named Drupal, but the hosting service's new empty (sql) db is called ihelpulearn. When the service support folks try to import Drupal.sql into the empty db on their server they get the following error:

---------------------------------- Read full article »