Author: mtredinnick
Date: 2007-11-15 03:21:36 -0600 (Thu, 15 Nov 2007)
New Revision: 6677
Modified:
django/trunk/docs/custom_model_fields.txt
Log:
Fixed #5892, #5930 -- Fixed some typos pointed out by [EMAIL PROTECTED] and
nickl.
Modified: django/trunk/docs/custom_model_fields.txt
===================================================================
--- django/trunk/docs/custom_model_fields.txt 2007-11-15 09:17:53 UTC (rev
6676)
+++ django/trunk/docs/custom_model_fields.txt 2007-11-15 09:21:36 UTC (rev
6677)
@@ -56,7 +56,7 @@
We assign to and retrieve from the ``hand`` attribute in our model just like
any other Python class. The trick is to tell Django how to handle saving and
-loading such an object
+loading such an object.
In order to use the ``Hand`` class in our models, we **do not** have to change
this class at all. This is ideal, because it means you can easily write
@@ -98,7 +98,7 @@
characters by concatenating all the cards together in a pre-determined order.
Say, all the *north* cards first, then the *east*, *south* and *west* cards, in
that order. So ``Hand`` objects can be saved to text or character columns in
-the database
+the database.
What does a field class do?
---------------------------
@@ -233,9 +233,9 @@
metaclass. This ensures that the ``to_python()`` method, documented below_,
will always be called when the attribute is initialised.
-Our ``HandleField`` class now looks like this::
+Our ``HandField`` class now looks like this::
- class HandleField(models.Field):
+ class HandField(models.Field):
__metaclass__ = models.SubfieldBase
def __init__(self, *args, **kwargs):
@@ -549,7 +549,7 @@
Some general advice
--------------------
-Writing a custom field can be a tricky process sometime, particularly if you
+Writing a custom field can be a tricky process sometimes, particularly if you
are doing complex conversions between your Python types and your database and
serialization formats. A couple of tips to make things go more smoothly:
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
