| .. |
|
basic
|
Fixed #5641 -- Handle lazy translations correctly when used as default arguments. Thanks, permon.
|
2007-10-04 01:55:51 +00:00 |
|
choices
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
custom_columns
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
custom_managers
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
custom_methods
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
custom_pk
|
Fixed #3703 -- Added pk property to models. Thanks, Collin Grady and jeromie@gmail.com.
|
2007-09-16 01:57:25 +00:00 |
|
empty
|
Fixed #6068 -- Updated docstrings in model tests to make the documentation
|
2007-12-01 21:18:45 +00:00 |
|
field_defaults
|
Fixed #5996 -- Add a pyscopg2 convertor for SafeUnicode -> unicode. Thanks, remco@diji.biz
|
2007-12-01 22:26:24 +00:00 |
|
field_subclassing
|
Fixed #5989 -- Fixed a problem with values being incorrectly reused by
|
2007-11-29 19:30:49 +00:00 |
|
fixtures
|
Fixed a typo. I think I should get full marks for getting all the letters right, but some people insist they should be in the right order, too.
|
2007-09-16 10:49:27 +00:00 |
|
generic_relations
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
get_latest
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
get_object_or_404
|
Fixed #3511 -- Changed QuerySet.get() to return a MultipleObjectsReturned exception, rather than an assertion error. Thanks, Gary Wilson and cheeming.
|
2007-12-02 18:21:07 +00:00 |
|
get_or_create
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
invalid_models
|
Fixed #3323 -- More robust error handling for related objetcs. Thanks, Greg
|
2007-12-02 18:10:07 +00:00 |
|
lookup
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
m2m_and_m2o
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
m2m_intermediary
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
m2m_multiple
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
m2m_recursive
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
m2o_recursive
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
m2o_recursive2
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
manipulators
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
many_to_many
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
many_to_one
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
many_to_one_null
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
model_forms
|
Fixed #4653 -- Improved the logic to decide when to include (and select as
|
2007-11-29 16:32:18 +00:00 |
|
model_inheritance
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
mutually_referential
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
one_to_one
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
or_lookups
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
ordering
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
pagination
|
Fixed #5932 -- Use `self.pages` and not `self._pages` in `_get_page_range` so that an exception is not raised if `self.page_range` is accessed before `self.pages`.
|
2007-11-19 06:10:23 +00:00 |
|
properties
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
reserved_names
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
reverse_lookup
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
save_delete_hooks
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
select_related
|
Fixed #6068 -- Updated docstrings in model tests to make the documentation
|
2007-12-01 21:18:45 +00:00 |
|
serializers
|
Fixed #6068 -- Updated docstrings in model tests to make the documentation
|
2007-12-01 21:18:45 +00:00 |
|
signals
|
Fixed #5559: instances sent via post-save signals no longer have pks of None. Thanks, Joseph Kocherhans.
|
2007-09-24 18:27:42 +00:00 |
|
str
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
test_client
|
Fixed #6068 -- Updated docstrings in model tests to make the documentation
|
2007-12-01 21:18:45 +00:00 |
|
transactions
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
user_commands
|
Fixed #6068 -- Updated docstrings in model tests to make the documentation
|
2007-12-01 21:18:45 +00:00 |
|
validation
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
__init__.py
|
MERGED MAGIC-REMOVAL BRANCH TO TRUNK. This change is highly backwards-incompatible. Please read http://code.djangoproject.com/wiki/RemovingTheMagic for upgrade instructions.
|
2006-05-02 01:31:56 +00:00 |
805c364fcf