mirror of
https://github.com/django/django.git
synced 2025-08-04 02:48:35 +00:00
Fixed #14091 - be more correct about logging queries in connection.queries.
Thanks to Aymeric Augustin for figuring out how to make this work across multiple databases. git-svn-id: http://code.djangoproject.com/svn/django/trunk@16081 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
598032b8c4
commit
5b0e4e49d4
7 changed files with 57 additions and 7 deletions
|
@ -465,7 +465,7 @@ itself to versions newer than the ones included with your particular Python
|
|||
binary distribution, if needed.
|
||||
|
||||
"Database is locked" errors
|
||||
-----------------------------------------------
|
||||
---------------------------
|
||||
|
||||
SQLite is meant to be a lightweight database, and thus can't support a high
|
||||
level of concurrency. ``OperationalError: database is locked`` errors indicate
|
||||
|
@ -506,6 +506,16 @@ If you're getting this error, you can solve it by:
|
|||
SQLite does not support the ``SELECT ... FOR UPDATE`` syntax. Calling it will
|
||||
have no effect.
|
||||
|
||||
.. _sqlite-connection-queries:
|
||||
|
||||
Parameters not quoted in ``connection.queries``
|
||||
-----------------------------------------------
|
||||
|
||||
``sqlite3`` does not provide a way to retrieve the SQL after quoting and
|
||||
substituting the parameters. Instead, the SQL in ``connection.queries`` is
|
||||
rebuilt with a simple string interpolation. It may be incorrect. Make sure
|
||||
you add quotes where necessary before copying a query into a SQLite shell.
|
||||
|
||||
.. _oracle-notes:
|
||||
|
||||
Oracle notes
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue