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


Ignore:
Timestamp:
Jul 29, 2018, 6:58:02 PM (6 years ago)
Author:
Ramiro Morales

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29610, comment 1

    v1 v2  
    1 If you want the raw SQL ``"%x"`` formatting specifier to reach the sqlite `printf` function you'll need to double the `%` so it gets passed "un-interpreted" by the query building stage.
     1If you want the raw SQL `"%x"` formatting specifier to reach the sqlite `printf` function you'll need to double the `%` so it gets passed "un-interpreted" by the query building stage.
    22
    33We have documentation about this requirement in other areas all of them related to raw SQL handling (circumventing the ORM):
     
    88* https://docs.djangoproject.com/en/2.0/ref/migration-operations/#runsql
    99
    10 It 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.
     10It 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.
    1111
    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.
Back to Top