Small formatting changes to model unit tests to make them look better in the model examples online
git-svn-id: http://code.djangoproject.com/svn/django/trunk@3030 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
3daae59aab
commit
a846155118
|
@ -1,5 +1,5 @@
|
|||
"""
|
||||
3. Giving models custom methods and custom managers
|
||||
3. Giving models custom methods
|
||||
|
||||
Any method you add to a model will be available to instances.
|
||||
"""
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
"""
|
||||
27. Many-to-many and many-to-one relationships to the same table.
|
||||
27. Many-to-many and many-to-one relationships to the same table
|
||||
|
||||
This is a response to bug #1535
|
||||
|
||||
|
@ -16,7 +16,7 @@ class Issue(models.Model):
|
|||
client = models.ForeignKey(User, related_name='test_issue_client')
|
||||
def __repr__(self):
|
||||
return "<Issue %d>" % (self.num,)
|
||||
|
||||
|
||||
class Meta:
|
||||
ordering = ('num',)
|
||||
|
||||
|
|
|
@ -1,21 +1,20 @@
|
|||
"""
|
||||
20. Object Pagination
|
||||
|
||||
Django provides a framework for paginating a list of objects in a few.
|
||||
This is often useful for dividing search results or long lists of objects
|
||||
in to easily readable pages.
|
||||
|
||||
28. Object pagination
|
||||
|
||||
Django provides a framework for paginating a list of objects in a few lines
|
||||
of code. This is often useful for dividing search results or long lists of
|
||||
objects into easily readable pages.
|
||||
"""
|
||||
|
||||
from django.db import models
|
||||
|
||||
class Article(models.Model):
|
||||
headline = models.CharField(maxlength=100, default='Default headline')
|
||||
pub_date = models.DateTimeField()
|
||||
|
||||
|
||||
def __repr__(self):
|
||||
return self.headline
|
||||
|
||||
return self.headline
|
||||
|
||||
API_TESTS = """
|
||||
# prepare a list of objects for pagination
|
||||
>>> from datetime import datetime
|
||||
|
@ -34,8 +33,8 @@ API_TESTS = """
|
|||
>>> paginator.pages
|
||||
2
|
||||
|
||||
# get the first page (zero-based)
|
||||
>>> paginator.get_page(0)
|
||||
# get the first page (zero-based)
|
||||
>>> paginator.get_page(0)
|
||||
[Article 1, Article 2, Article 3, Article 4, Article 5]
|
||||
|
||||
# get the second page
|
||||
|
@ -45,7 +44,7 @@ API_TESTS = """
|
|||
# does the first page have a next or previous page?
|
||||
>>> paginator.has_next_page(0)
|
||||
True
|
||||
|
||||
|
||||
>>> paginator.has_previous_page(0)
|
||||
False
|
||||
|
||||
|
@ -55,5 +54,5 @@ False
|
|||
|
||||
>>> paginator.has_previous_page(1)
|
||||
True
|
||||
|
||||
|
||||
"""
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
"""
|
||||
XXX. Transactions
|
||||
15. Transactions
|
||||
|
||||
Django handles transactions in three different ways. The default is to commit
|
||||
each transaction upon a write, but you can decorate a function to get
|
||||
|
|
|
@ -1,5 +1,7 @@
|
|||
"""
|
||||
XX. Validation
|
||||
29. Validation
|
||||
|
||||
This is an experimental feature!
|
||||
|
||||
Each model instance has a validate() method that returns a dictionary of
|
||||
validation errors in the instance's fields. This method has a side effect
|
||||
|
|
Loading…
Reference in New Issue