#36882: Add debug instrumentation for callproc() in CursorDebugWrapper
-------------------------------------+-------------------------------------
Reporter: akshaytheflash | Type: Bug
Status: new | Component: Database
| layer (models, ORM)
Version: 6.0 | Severity: Normal
Keywords: callproc, debug, | Triage Stage:
logging, stored procedures | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
The callproc() method in CursorDebugWrapper is not currently instrumented
for debug logging, unlike execute() and executemany(). This means stored
procedure calls are not logged when DEBUG=True.
This patch adds the callproc() method to CursorDebugWrapper to log
procedure calls with timing information, consistent with how other
database operations are logged.
The fix includes:
- Implementation of callproc() in CursorDebugWrapper
- Test to verify the instrumentation works correctly
- Removal of the "XXX callproc isn't instrumented" comment
--
Ticket URL: <https://code.djangoproject.com/ticket/36882>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019befea04d7-0780c4e0-2f54-4f30-8f57-5e7c479d5de7-000000%40eu-central-1.amazonses.com.
