Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

Improved examples in docs about raw SQL queries.

Browse Source 
Regression in 14459f80ee3a9e005989db37c26fd13bb6d2fab2.
This commit is contained in:
Mariusz Felisiak 2023-04-20 12:24:33 +02:00 committed by GitHub
parent 0494efddc4
commit 498195bda4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/topics/db/sql.txt
View File

@ -121,11 +121,13 @@ had ``Person`` data in it, you could easily map it into ``Person`` instances:
.. code-block:: pycon .. code-block:: pycon
>>> Person.objects.raw( >>> Person.objects.raw(
... """SELECT first AS first_name, ... """
... SELECT first AS first_name,
... last AS last_name, ... last AS last_name,
... bd AS birth_date, ... bd AS birth_date,
... pk AS id, ... pk AS id,
... FROM some_other_table""" ... FROM some_other_table
... """
... ) ... )
As long as the names match, the model instances will be created correctly. As long as the names match, the model instances will be created correctly.
@ -175,8 +177,9 @@ fields that are omitted from the query will be loaded on demand. For example:
>>> for p in Person.objects.raw("SELECT id, first_name FROM myapp_person"): >>> for p in Person.objects.raw("SELECT id, first_name FROM myapp_person"):
... print( ... print(
... p.first_name, p.last_name # This will be retrieved by the original query ... p.first_name, # This will be retrieved by the original query
... ) # This will be retrieved on demand ... p.last_name, # This will be retrieved on demand
... )
... ...
John Smith John Smith
Jane Jones Jane Jones