Changeset 6677
- Timestamp:
- 11/15/07 03:21:36 (10 months ago)
- Files:
-
- django/trunk/docs/custom_model_fields.txt (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/custom_model_fields.txt
r6652 r6677 57 57 We assign to and retrieve from the ``hand`` attribute in our model just like 58 58 any other Python class. The trick is to tell Django how to handle saving and 59 loading such an object 59 loading such an object. 60 60 61 61 In order to use the ``Hand`` class in our models, we **do not** have to change … … 99 99 Say, all the *north* cards first, then the *east*, *south* and *west* cards, in 100 100 that order. So ``Hand`` objects can be saved to text or character columns in 101 the database 101 the database. 102 102 103 103 What does a field class do? … … 234 234 will always be called when the attribute is initialised. 235 235 236 Our ``Hand leField`` class now looks like this::237 238 class Hand leField(models.Field):236 Our ``HandField`` class now looks like this:: 237 238 class HandField(models.Field): 239 239 __metaclass__ = models.SubfieldBase 240 240 … … 550 550 -------------------- 551 551 552 Writing a custom field can be a tricky process sometime , particularly if you552 Writing a custom field can be a tricky process sometimes, particularly if you 553 553 are doing complex conversions between your Python types and your database and 554 554 serialization formats. A couple of tips to make things go more smoothly:
