Changes between Version 52 and Version 53 of RemovingTheMagic

Timestamp:

Jan 25, 2006, 9:07:11 AM (18 years ago)

Author:

Adrian Holovaty

Comment:

Added PostgreSQL upgrade instructions

RemovingTheMagic

@@ -15 +15 @@
 === Rename core database tables ===
 
-We've renamed a bunch of the core Django tables. To upgrade, execute this SQL in your database:
+We've renamed a bunch of the core Django tables. To upgrade in MySQL and SQLite, execute this SQL in your database:
 
 {{{
@@ -34 +34 @@
 }}}
 
-WorldMaker: It seems that I needed to rename the associated id sequences (in Postgres) as well.  Is this standard?  Should this be added to the above SQL?  It should impact PostgreSQL installations the most, and apparently several versions won't properly rename the sequences.
+PostgreSQL is different, because you have to rename sequences, too. To upgrade in PostgreSQL, execute this SQL in your database:
+
+{{{
+BEGIN;
+
+ALTER TABLE auth_groups RENAME TO auth_group;
+ALTER TABLE auth_groups_id_seq RENAME TO auth_group_id_seq;
+ALTER TABLE auth_group ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE auth_group ALTER COLUMN id SET DEFAULT nextval('public.auth_group_id_seq'::text);
+
+ALTER TABLE auth_groups_permissions RENAME TO auth_group_permissions;
+ALTER TABLE auth_groups_permissions_id_seq RENAME TO auth_group_permissions_id_seq;
+ALTER TABLE auth_group_permissions ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE auth_group_permissions ALTER COLUMN id SET DEFAULT nextval('public.auth_group_permissions_id_seq'::text);
+
+ALTER TABLE auth_messages RENAME TO auth_message;
+ALTER TABLE auth_messages_id_seq RENAME TO auth_message_id_seq;
+ALTER TABLE auth_message ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE auth_message ALTER COLUMN id SET DEFAULT nextval('public.auth_message_id_seq'::text);
+
+ALTER TABLE auth_permissions RENAME TO auth_permission;
+ALTER TABLE auth_permissions_id_seq RENAME TO auth_permission_id_seq;
+ALTER TABLE auth_permission ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE auth_permission ALTER COLUMN id SET DEFAULT nextval('public.auth_permission_id_seq'::text);
+
+ALTER TABLE auth_users RENAME TO auth_user;
+ALTER TABLE auth_users_id_seq RENAME TO auth_user_id_seq;
+ALTER TABLE auth_user ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE auth_user ALTER COLUMN id SET DEFAULT nextval('public.auth_user_id_seq'::text);
+
+ALTER TABLE auth_users_groups RENAME TO auth_user_groups;
+ALTER TABLE auth_users_groups_id_seq RENAME TO auth_user_groups_id_seq;
+ALTER TABLE auth_user_groups ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE auth_user_groups ALTER COLUMN id SET DEFAULT nextval('public.auth_user_groups_id_seq'::text);
+
+ALTER TABLE auth_users_user_permissions RENAME TO auth_user_user_permissions;
+ALTER TABLE auth_users_user_permissions_id_seq RENAME TO auth_user_user_permissions_id_seq;
+ALTER TABLE auth_user_user_permissions ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE auth_user_user_permissions ALTER COLUMN id SET DEFAULT nextval('public.auth_user_user_permissions_id_seq'::text);
+
+ALTER TABLE content_types RENAME TO django_content_type;
+ALTER TABLE content_types_id_seq RENAME TO django_content_type_id_seq;
+ALTER TABLE django_content_type ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE django_content_type ALTER COLUMN id SET DEFAULT nextval('public.django_content_type_id_seq'::text);
+
+ALTER TABLE core_sessions RENAME TO django_session;
+
+ALTER TABLE django_flatpages RENAME TO django_flatpage;
+ALTER TABLE django_flatpages_id_seq RENAME TO django_flatpage_id_seq;
+ALTER TABLE django_flatpage ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE django_flatpage ALTER COLUMN id SET DEFAULT nextval('public.django_flatpage_id_seq'::text);
+
+ALTER TABLE django_flatpages_sites RENAME TO django_flatpage_sites;
+ALTER TABLE django_flatpages_sites_id_seq RENAME TO django_flatpage_sites_id_seq;
+ALTER TABLE django_flatpage_sites ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE django_flatpage_sites ALTER COLUMN id SET DEFAULT nextval('public.django_flatpage_sites_id_seq'::text);
+
+ALTER TABLE django_redirects RENAME TO django_redirect;
+ALTER TABLE django_redirects_id_seq RENAME TO django_redirect_id_seq;
+ALTER TABLE django_redirect ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE django_redirect ALTER COLUMN id SET DEFAULT nextval('public.django_redirect_id_seq'::text);
+
+ALTER TABLE packages RENAME TO django_package;
+
+ALTER TABLE sites RENAME TO django_site;
+ALTER TABLE sites_id_seq RENAME TO django_site_id_seq;
+ALTER TABLE django_site ALTER COLUMN id DROP DEFAULT;
+ALTER TABLE django_site ALTER COLUMN id SET DEFAULT nextval('public.django_site_id_seq'::text);
+
+COMMIT;
+}}}
 
 === Database table-naming scheme has been changed ===
@@ -44 +114 @@
 As always, this behavior can be overridden on a per-model basis by specifying the {{{db_table}}} attribute in {{{class Meta}}} in your model.
 
-To upgrade, you'll either have to explicitly set {{{db_table}}} in your models or rename your database tables to fit the new naming scheme Django expects.
+To upgrade, you'll either have to explicitly set {{{db_table}}} in your models or rename your database tables to fit the new naming scheme Django expects. We'd recommend setting {{{db_table}}}, because it's easier.