Debian Codegraph @

docs/faq/models.txt

raw
1 =========================
2 FAQ: Databases and models
3 =========================
4
5 .. _faq-see-raw-sql-queries:
6
7 How can I see the raw SQL queries Django is running?
8 ====================================================
9
10 Make sure your Django :setting:`DEBUG` setting is set to ``True``.
11 Then do this:
12
13 .. code-block:: pycon
14
15 >>> from django.db import connection
16 >>> connection.queries
17 [{'sql': 'SELECT polls_polls.id, polls_polls.question, polls_polls.pub_date FROM polls_polls',
18 'time': '0.002'}]
19
20 ``connection.queries`` is only available if :setting:`DEBUG` is ``True``.
21 It's a list of dictionaries in order of query execution. Each dictionary has
22 the following:
23
24 * ``sql`` - The raw SQL statement
25 * ``time`` - How long the statement took to execute, in seconds.
26
27 ``connection.queries`` includes all SQL statements -- INSERTs, UPDATES,
28 SELECTs, etc. Each time your app hits the database, the query will be recorded.
29
30 If you are using :doc:`multiple databases</topics/db/multi-db>`, you can use the
31 same interface on each member of the ``connections`` dictionary:
32
33 .. code-block:: pycon
34
35 >>> from django.db import connections
36 >>> connections["my_db_alias"].queries
37
38 If you need to clear the query list manually at any point in your functions,
39 call ``reset_queries()``, like this::
40
41 from django.db import reset_queries
42
43 reset_queries()
44
45 Can I use Django with a preexisting database?
46 =============================================
47
48 Yes. See :doc:`Integrating with a legacy database </howto/legacy-databases>`.
49
50 If I make changes to a model, how do I update the database?
51 ===========================================================
52
53 Take a look at Django's support for :mod:`schema migrations
54 <django.db.migrations>`.
55
56 If you don't mind clearing data, your project's ``manage.py`` utility has a
57 :djadmin:`flush` option to reset the database to the state it was in
58 immediately after :djadmin:`migrate` was executed.
59
60 Do Django models support multiple-column primary keys?
61 ======================================================
62
63 No. Only single-column primary keys are supported.
64
65 But this isn't an issue in practice, because there's nothing stopping you from
66 adding other constraints (using the ``unique_together`` model option or
67 creating the constraint directly in your database), and enforcing the
68 uniqueness at that level. Single-column primary keys are needed for things such
69 as the admin interface to work; e.g., you need a single value to specify
70 an object to edit or delete.
71
72 Does Django support NoSQL databases?
73 ====================================
74
75 NoSQL databases are not officially supported by Django itself. There are,
76 however, a number of side projects and forks which allow NoSQL functionality in
77 Django.
78
79 You can take a look on `the wiki page`_ which discusses some projects.
80
81 .. _the wiki page: https://code.djangoproject.com/wiki/NoSqlSupport
82
83 How do I add database-specific options to my CREATE TABLE statements, such as specifying MyISAM as the table type?
84 ==================================================================================================================
85
86 We try to avoid adding special cases in the Django code to accommodate all the
87 database-specific options such as table type, etc. If you'd like to use any of
88 these options, create a migration with a
89 :class:`~django.db.migrations.operations.RunSQL` operation that contains
90 ``ALTER TABLE`` statements that do what you want to do.
91
92 For example, if you're using MySQL and want your tables to use the MyISAM table
93 type, use the following SQL:
94
95 .. code-block:: sql
96
97 ALTER TABLE myapp_mytable ENGINE=MyISAM;