Changes between Version 264 and Version 265 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Sep 24, 2008, 5:29:07 PM (16 years ago)
Author:
Karen Tracey
Comment:

Fix some links that went nowhere (pointed to old doc pages)

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v264 v265  
    9696}}}
    9797should be modified to read:
     98
     99
    98100
    99101{{{
     
    10601062In [8191], several deprecated features were removed:
    10611063
    1062  * The "simple" cache backend was removed, use the [http://www.djangoproject.com/documentation/cache/#local-memory-caching "locmem" backend] instead.
     1064 * The "simple" cache backend was removed, use the [http://docs.djangoproject.com/en/dev/topics/cache/#local-memory-caching "locmem" backend] instead.
    10631065 * The `ObjectPaginator` class was removed, use the new [http://www.djangoproject.com/documentation/pagination/ Paginator and Page classes] instead.
    1064  * The `edit_inline_type` argument for `ForeignKey` fields was removed, use [http://www.djangoproject.com/documentation/admin/#inlinemodeladmin-objects InlineModelAdmin] instead.
    1065  * The `QOperator`, `QNot`, `QAnd` and `QOr` classes were removed, use the [http://www.djangoproject.com/documentation/db-api/#complex-lookups-with-q-objects Q class] instead.
     1066 * The `edit_inline_type` argument for `ForeignKey` fields was removed, use [http://docs.djangoproject.com/en/dev/ref/contrib/admin/#inlinemodeladmin-objects InlineModelAdmin] instead.
     1067 * The `QOperator`, `QNot`, `QAnd` and `QOr` classes were removed, use the [http://docs.djangoproject.com/en/dev/topics/db/queries/#complex-lookups-with-q-objects Q class] instead.
    10661068 * The `maxlength` argument for model fields was removed, use `max_length` instead.
    10671069
Back to Top