Quote:
Originally Posted by Chuck S How do you know your gallery has an issue at all if you dont know what tables are affected? You should be having errors which you would be posting here
16 out of 21 mysql tables in Photopost use auto_increment.
ALTER TABLE `pp_admlog` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_favorites` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_categories` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_comments` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_photos` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_settings` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_sort` CHANGE `sortid` `sortid` INT( 15 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_admingroups` CHANGE `id` `id` INT( 3 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_sortmem` CHANGE `sortid` `sortid` INT( 3 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_ecards` CHANGE `id` `id` INT( 25 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_notify` CHANGE `id` `id` INT( 15 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_users` CHANGE `userid` `userid` INT( 25 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_ipcache` CHANGE `id` `id` INT( 10 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_extrafields` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_photoextras` CHANGE `id` `id` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE `pp_usergroups` CHANGE `groupid` `groupid` INT( 12 ) UNSIGNED NOT NULL AUTO_INCREMENT;
EDIT: posting responses at the same time these above should help |
Just for anyone else having problems when moving from a newer version of mysql to an older version and losing the auto increment bit from the database, this post has been invaluble to me in fixing that problem, so a personal thanks from me regarding this one.
I moved from a host with mysql 4.1.19 to one with mysql 4.0.25 and this thread helped me fix the problem.