mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-01 10:59:12 +00:00
Code Issues 32 Releases Wiki Activity

Fixed #2064 -- Added 'Falling back to raw SQL' section to docs/db-api.txt

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@3054 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-06-02 04:04:04 +00:00
parent fe4139de31
commit 1717b94fc8
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/db-api.txt
View File

@ -1578,3 +1578,23 @@ get_FOO_height() and get_FOO_width()
For every ``ImageField``, the object will have ``get_FOO_height()`` and For every ``ImageField``, the object will have ``get_FOO_height()`` and
``get_FOO_width()`` methods, where ``FOO`` is the name of the field. This ``get_FOO_width()`` methods, where ``FOO`` is the name of the field. This
returns the height (or width) of the image, as an integer, in pixels. returns the height (or width) of the image, as an integer, in pixels.
Falling back to raw SQL
=======================
If you find yourself needing to write an SQL query that is too complex for
Django's database-mapper to handle, you can fall back into raw-SQL statement
mode.
The preferred way to do this is by giving your model custom methods or custom
manager methods that execute queries. Although there's nothing in Django that
*requires* database queries to live in the model layer, this approach keeps all
your data-access logic in one place, which is smart from an code-organization
standpoint. For instructions, see `Executing custom SQL`_.
Finally, it's important to note that the Django database layer is merely an
interface to your database. You can access your database via other tools,
programming languages or database frameworks; there's nothing Django-specific
about your database.
.. _Executing custom SQL: http://www.djangoproject.com/documentation/model_api/#executing-custom-sql