Author: brosner
Date: Fri Nov 14 11:34:28 2008
New Revision: 1081

Modified:
    wiki/BackwardsIncompatibleChanges.wiki

Log:
Added the zwitschern -> microblogging change.

Modified: wiki/BackwardsIncompatibleChanges.wiki
==============================================================================
--- wiki/BackwardsIncompatibleChanges.wiki      (original)
+++ wiki/BackwardsIncompatibleChanges.wiki      Fri Nov 14 11:34:28 2008
@@ -121,6 +121,26 @@
  )
  }}}

+=== Revision 1199 - 1201 (November 12, 2008) ===
+
+The interal app `zwitschern` has been externalized as `microblogging` in  
the django-microblogging project. This change will require the following  
SQL migration:
+
+{{{
+BEGIN;
+
+-- table renames
+ALTER TABLE zwitschern_tweet
+    RENAME TO microblogging_tweet;
+ALTER TABLE zwitschern_tweetinstance
+    RENAME TO microblogging_tweetinstance;
+ALTER TABLE zwitschern_following
+    RENAME TO microblogging_following;
+
+COMMIT;
+}}}
+
+All references to `zwitschern` should be replaced with `microblogging`.  
This change is still in progress and can have more backward incompatible  
changes. `microblogging` is literally an exact copy of `zwitschern` so  
everything should work as is once the references have been fixed.
+
  === Revision 1204 (November 13, 2008) ===

  OpenID support underwent a bit of fixing. Before this change we had a  
forked branch from django-openid. They were in local_apps  
(django_openidauth and django_openidconsumer). They have been removed in  
favor of the trunk version of django-openid that was recently refactored by  
Simon Willison. It is now a standard external_app reference.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pinax-updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pinax-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to