Skip to content
Browse files

Remove old SQL update scripts.

  • Loading branch information...
1 parent 9f5fa8d commit 203417fb69f928c0ee4b47a165260e90f319ffd7 @aaugustin aaugustin committed
Showing with 0 additions and 52 deletions.
  1. +0 −36 django_website/upgrade/add_community.sql
  2. +0 −16 django_website/upgrade/upgrade-to-1.0.sql
36 django_website/upgrade/add_community.sql
@@ -1,36 +0,0 @@
--- Upgrade the DB from the version running on the old
--- djangoproject server to this new community version.
--- If we don't do this then we can't do the final SET NOT NULL
--- step below in the same transaction.
--- Create the feed type table.
--- Same as running syncdb, but a little more visible.
-CREATE TABLE "aggregator_feedtype" (
- "id" serial NOT NULL PRIMARY KEY,
- "name" varchar(250) NOT NULL,
- "slug" varchar(250) NOT NULL,
- "can_self_add" boolean NOT NULL
--- Create the "blog post" feed type for the old entries in the DB.
--- This'll get smooshed by the fixture (community_seed.json),
--- but we need it here to move old data over cleanly.
-INSERT INTO aggregator_feedtype (id, name, slug, can_self_add)
- VALUES (2, 'Community Blog Posts', 'community-blog-posts', 't');
--- Add the feed_type_id column to aggregator_feeds and update it
--- to point to the new feed type.
-ALTER TABLE aggregator_feeds ADD COLUMN feed_type_id integer
-UPDATE aggregator_feeds SET feed_type_id = 2;
-ALTER TABLE aggregator_feeds ALTER COLUMN feed_type_id SET NOT NULL;
16 django_website/upgrade/upgrade-to-1.0.sql
@@ -1,16 +0,0 @@
-delete from django_admin_log;
-delete from comments_freecomment where content_type_id = 13;
-INSERT INTO django_comments
- (content_type_id, object_pk, site_id, user_name, user_email, user_url,
- comment, submit_date, ip_address, is_public, is_removed)
- content_type_id, object_id, site_id, person_name, '', '', comment,
- submit_date, ip_address, is_public, approved
-FROM comments_freecomment;
-drop table comments_freecomment;
-drop table comments_comment cascade;

0 comments on commit 203417f

Please sign in to comment.
Something went wrong with that request. Please try again.