Provide an option to collect a full backtrace including arguments in database event logging

Created on 15 November 2023, about 1 year ago

Updated 17 November 2023, about 1 year ago

Problem/Motivation

In 📌 Allow assertions on the number of database queries run during tests RTBC we added DEBUG_BACKTRACE_IGNORE_ARGS to thehere database logging events - this was apparently an oversight according to @mondrake so treating it as a bug in that issue.

It's possible that someone might want to access the full backtrace with all the arguments, so opening this as a feature request to provide this as an option.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

✨ Feature request

Status

Needs work

Version

11.0 🔥

Component

Database →

Last updated about 4 hours ago

Maintained by
🇳🇱Netherlands @daffie

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.

Needs Review Queue Initiative
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.

Needs tests
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Needs change record
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Comments & Activities

Issue created by @catch
First commit to issue fork.
@mondrake opened merge request.
Status changed to Needs review about 1 year ago8:10pm 16 November 2023
Comment about 1 year ago →
🇮🇹Italy mondrake 🇮🇹
Here's a MR
Status changed to Needs work about 1 year ago2:34pm 17 November 2023
Comment about 1 year ago →
🇺🇸United States smustgrave
From what I can tell it makes sense to me

Think it could have simple test coverage assertion added though, and not sure if it warrants a CR but tagging just in case.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024