Changes between Version 2 and Version 3 of Ticket #29610, comment 1


Ignore:
Timestamp:
Jul 30, 2018, 7:59:34 AM (6 years ago)
Author:
Tim Graham

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #29610, comment 1

    v2 v3  
    33We have documentation about this requirement in other areas all of them related to raw SQL handling (circumventing the ORM):
    44
    5 * https://docs.djangoproject.com/en/2.0/topics/db/sql/#executing-custom-sql-directly
    6 * https://docs.djangoproject.com/en/2.0/releases/1.6/#percent-literals-in-cursor-execute-queries
    7 * https://docs.djangoproject.com/en/2.0/releases/1.7.1/#bugfixes (search for 'percent')
    8 * https://docs.djangoproject.com/en/2.0/ref/migration-operations/#runsql
     5* https://docs.djangoproject.com/en/dev/topics/db/sql/#executing-custom-sql-directly
     6* https://docs.djangoproject.com/en/dev/releases/1.6/#percent-literals-in-cursor-execute-queries
     7* https://docs.djangoproject.com/en/dev/releases/1.7.1/#bugfixes (search for 'percent')
     8* https://docs.djangoproject.com/en/dev/ref/migration-operations/#runsql
    99
    1010It could argued a similar note should be added to the `connection.cursor.db.ops.last_executed_query()` docs but currently it isn't documented, which IMHO isn't strange as it isn't a public API at all.
    … …  
    1212Do we want it to be a public API? The answer to this question would decide if this ticket should be converted to a documentation issue or closed as wontfix.
    1313
    14 Or we could accept a patch for the ``last_executed_query()`` docstring.
     14Or we could accept a patch for the `last_executed_query()` docstring.
Back to Top