diff options
| author | Tim Graham <timograham@gmail.com> | 2015-08-12 09:26:57 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-09-23 19:31:09 -0400 |
| commit | 08ab262649fc483df71d860d217a864ecbbcc69d (patch) | |
| tree | 9315a1de8d5d56ea1be416b491e44976a150c30f /docs | |
| parent | 4fd264b6f1737b0317fdd95b3d7ff3bba15ae6c3 (diff) | |
Removed SubfieldBase per deprecation timeline.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/howto/custom-model-fields.txt | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index 721154668f..ab36031fc0 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -428,13 +428,6 @@ get out of the way. Converting values to Python objects ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionchanged:: 1.8 - - Historically, Django provided a metaclass called ``SubfieldBase`` which - always called :meth:`~Field.to_python` on assignment. This did not play - nicely with custom database transformations, aggregation, or values - queries, so it has been replaced with :meth:`~Field.from_db_value`. - If your custom :class:`~Field` class deals with data structures that are more complex than strings, dates, integers, or floats, then you may need to override :meth:`~Field.from_db_value` and :meth:`~Field.to_python`. |