Changes between Version 3 and Version 4 of BackwardsIncompatibleChanges

Timestamp:

Aug 10, 2005, 2:40:35 PM (19 years ago)

Author:

Adrian Holovaty

Comment:

Added note about admin log change from [469].

BackwardsIncompatibleChanges

@@ -41 +41 @@
 We'll stop supporting the old syntax for Django's first release.
 
-== Upcoming changes ==
+=== Changed admin log to store primary keys as TEXT fields, not INTEGER fields ===
+
+As of [469], the {{{object_id}}} field in {{{django.models.auth.LogEntry}}} is a {{{TextField}}} instead of an {{{IntegerField}}}. We made this change to accomodate non-integer primary keys.
+
+If you're using a Django database installation from before [469] and you want to use non-integer primary keys on an object you edit in the admin site, you'll need to do an {{{ALTER TABLE}}} in your database.
+
+In PostgreSQL:
+
+{{{
+BEGIN;
+ALTER TABLE auth_admin_log RENAME object_id TO object_id_old;
+ALTER TABLE auth_admin_log ADD COLUMN object_id TEXT;
+UPDATE auth_admin_log SET object_id = object_id_old;
+ALTER TABLE auth_admin_log DROP COLUMN object_id_old;
+COMMIT;
+}}}
+
+In MySQL:
+
+{{{
+ALTER TABLE auth_admin_log MODIFY object_id TEXT;
+}}}
+
+== Possible upcoming changes ==
 
 === Model syntax ===
 
-This is the big one. Model syntax will be changed dramatically before Django's first release. See #122 for full information and discussion.
+This is the big one. Model syntax 'might' be changed dramatically before Django's first release, but this is still under debate. See #122 for full information and discussion.