From 08ab262649fc483df71d860d217a864ecbbcc69d Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 12 Aug 2015 09:26:57 -0400 Subject: Removed SubfieldBase per deprecation timeline. --- docs/howto/custom-model-fields.txt | 7 ------- 1 file changed, 7 deletions(-) (limited to 'docs') 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`. -- cgit v1.3