Code

Changes between Version 3 and Version 4 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
08/10/05 12:40:35 (9 years ago)
Author:
adrian
Comment:

Added note about admin log change from [469].

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v3 v4  
    4141We'll stop supporting the old syntax for Django's first release. 
    4242 
    43 == Upcoming changes == 
     43=== Changed admin log to store primary keys as TEXT fields, not INTEGER fields === 
     44 
     45As 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. 
     46 
     47If 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. 
     48 
     49In PostgreSQL: 
     50 
     51{{{ 
     52BEGIN; 
     53ALTER TABLE auth_admin_log RENAME object_id TO object_id_old; 
     54ALTER TABLE auth_admin_log ADD COLUMN object_id TEXT; 
     55UPDATE auth_admin_log SET object_id = object_id_old; 
     56ALTER TABLE auth_admin_log DROP COLUMN object_id_old; 
     57COMMIT; 
     58}}} 
     59 
     60In MySQL: 
     61 
     62{{{ 
     63ALTER TABLE auth_admin_log MODIFY object_id TEXT; 
     64}}} 
     65 
     66== Possible upcoming changes == 
    4467 
    4568=== Model syntax === 
    4669 
    47 This is the big one. Model syntax will be changed dramatically before Django's first release. See #122 for full information and discussion. 
     70This 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.