Author: Alex Date: 2009-12-22 08:37:16 -0600 (Tue, 22 Dec 2009) New Revision: 11947
Modified: django/branches/soc2009/multidb/docs/howto/custom-model-fields.txt Log: [soc2009/multidb] Added versionadded tags to custom model field docs. Patch from Russell Keith-Magee. Modified: django/branches/soc2009/multidb/docs/howto/custom-model-fields.txt =================================================================== --- django/branches/soc2009/multidb/docs/howto/custom-model-fields.txt 2009-12-22 14:37:09 UTC (rev 11946) +++ django/branches/soc2009/multidb/docs/howto/custom-model-fields.txt 2009-12-22 14:37:16 UTC (rev 11947) @@ -290,6 +290,9 @@ .. method:: db_type(self, connection) +.. versionadded:: 1.2 + The ``connection`` argument was added to support multiple databases. + Returns the database column data type for the :class:`~django.db.models.Field`, taking into account the connection object, and the settings associated with it. @@ -426,6 +429,9 @@ .. method:: get_prep_value(self, value) +.. versionadded:: 1.2 + This method was factored out of ``get_db_prep_value()`` + This is the reverse of :meth:`to_python` when working with the database backends (as opposed to serialization). The ``value`` parameter is the current value of the model's attribute (a field has @@ -451,6 +457,9 @@ .. method:: get_db_prep_value(self, value, connection, prepared=False) +.. versionadded:: 1.2 + The ``connection`` and ``prepared arguments were added to support multiple databases. + Some data types (for example, dates) need to be in a specific format before they can be used by a database backend. :meth:`get_db_prep_value` is the method where those conversions should @@ -467,6 +476,9 @@ .. method:: get_db_prep_save(self, value, connection) +.. versionadded:: 1.2 + The ``connection`` argument was added to support multiple databases. + Same as the above, but called when the Field value must be *saved* to the database. As the default implementation just calls ``get_db_prep_value``, you shouldn't need to implement this method @@ -505,6 +517,9 @@ .. method:: get_prep_lookup(self, lookup_type, value) +.. versionadded:: 1.2 + This method was factored out of ``get_db_prep_lookup()`` + :meth:`get_prep_lookup` performs the first phase of lookup preparation, performing generic data validity checks @@ -553,6 +568,9 @@ .. method:: get_db_prep_lookup(self, lookup_type, value, connection, prepared=False) +.. versionadded:: 1.2 + The ``connection`` and ``prepared`` arguments were added to support multiple databases. + Performs any database-specific data conversions required by a lookup. As with :meth:`get_db_prep_value`, the specific connection that will be used for the query is passed as the ``connection`` parameter. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
