Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Documentation markup fixes.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11956 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 0f2f08a7d78e3cff15bf98725f173f2e3382de0a 1 parent 5e54f6b
@freakboy3742 freakboy3742 authored
View
2  docs/howto/custom-model-fields.txt
@@ -458,7 +458,7 @@ Converting query values to database values
.. method:: get_db_prep_value(self, value, connection, prepared=False)
.. versionadded:: 1.2
- The ``connection`` and ``prepared arguments were added to support multiple databases.
+ 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.
View
8 docs/topics/db/multi-db.txt
@@ -28,7 +28,9 @@ whatever alias you choose.
The following is an example ``settings.py`` snippet defining two
databases - a default Postgres database, and a MySQL database called
-``users``::
+``users``:
+
+.. code-block:: python
DATABASES = {
'default': {
@@ -56,7 +58,9 @@ It is possible to select the database for a ``QuerySet`` at any point
during it's construction. To choose the database that a query will be
preformed against simply call the ``using()`` method on the
``QuerySet``. ``using()`` takes a single argument: the alias of the
-database on which you want to run the query. For example::
+database on which you want to run the query. For example:
+
+.. code-block:: python
# This will run on the 'default' database...
>>> Author.objects.all()
Please sign in to comment.
Something went wrong with that request. Please try again.