Good question... I dunno what is the answer to your question. I'll do some Googling and get back to you if I bump into an answer. You should email the people at iPage as they probably could answer your iPage question..
Yea, I get the same problem. Please help us..
You will need to use a program such as mysql_diff which you will find in the extras folder...
Does the MySQL Diff program fix the problem or just highlight the errors?..
It will list all changes in the DB structure from one database to another..
Ok, I used the mysqldiff to convert the old database to the new database format then I copied and pasted the output into the phpmyadmin query window but I get the following error..
ALTER TABLE `address_book` ALTER `address_book_id` DROP DEFAULT,.
ADD INDEX `idx_address_book_customers_id` ( `customers_id` ) ,.
DROP PRIMARY KEY ,.
ADD PRIMARY KEY ( `address_book_id` ).
#1062 - Duplicate entry '1' for key 1.
This is similar to the error I was getting when I would try and copy the data. What am I doing wrong?..
Can you elaborate? I thought easypopulate only did the catalog not the customer information...
Hate to do it but getting a bit desperate.
I was working on some upgrades to my iPage site and I have run into some difference in how the Address table works in my release versus others I have worked on..
The database I am working on is version 2.2-CVS rather than 2.2 MS2 which I am used to..
An example of what I am dealing with is this..
In the address table my current structure is:.
`address_book_id` int(11) NOT NULL default '1',.
The structure from others is:.
`address_book_id` int(11) NOT NULL auto_increment,.
Also, in the same table I get this from the current database:.
PRIMARY KEY (`address_book_id`,`customers_id`).
Rather than this in the other version:.
PRIMARY KEY (`address_book_id`),.
KEY `idx_address_book_customers_id` (`customers_id`).
) TYPE=MyISAM AUTO_INCREMENT=5;.
Any ideas what I am dealing with? I am a bit lost at this point. Would like to convert the 2.2-CVS to 2.2 MS2.
Well, here is some more detail on the problem..
The new way is that the customer ID in the adress book matches the customer in the customer table. each additional address a customer has.
A unique adress ID..
Address _id customer ID.
23 19 name and address 1.
24 19 name and address 2.
19 name and address 1.
Each customer can have only one entry in the customer table per email address, but can have multiple address in the address book, upto the limit set in admin..
Quesiton is since my install was a CVS install what is the best way to fix the database? (Please dont say manually scrubbing of data....please)..