- Status changed to RTBC
almost 2 years ago 1:44pm 16 January 2023 - Assigned to mondrake
- Status changed to Needs work
almost 2 years ago 7:02am 20 January 2023 - Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 10:52am 20 January 2023 - Status changed to RTBC
almost 2 years ago 7:41am 22 January 2023 - ๐ณ๐ฑNetherlands daffie
Adding the ID of the StatementInterface object as returned by spl_object_id() is to me a good idea.
There is testing added for the extra functionality.
Back to RTBC. - ๐บ๐ธUnited States mfb San Francisco
Wow this is amazing, thanks for running w/ this feature request! I'm now able to monitor db queries as they execute and build a nice hierarchical view of operations - see attached screenshot. I noticed that database logging didn't work until I cleared caches (not really a problem, just saying).
- ๐บ๐ธUnited States mfb San Francisco
Added a little release note snippet, feel free to edit.
- ๐ฌ๐งUnited Kingdom catch
#35 looks exciting! Adding tags for release notes + highlights. Haven't reviewed this enough to be able to commit it yet. What I did review didn't raise any massive flags - don't see a way around the \Drupal:: calls, and making it conditional on events being enabled at all is a good plan.
- Status changed to Fixed
almost 2 years ago 4:11pm 16 March 2023 - ๐ฌ๐งUnited Kingdom catch
This will also be useful for ๐ฑ Automated performance testing for core Active , not that it's anywhere close but I've started working on it again after a decade.
Reviewed again and couldn't find anything to complain about. Going to untag for release notes because there's nothing really for site owners here, but we can leave it tagged for highlights as an API improvement - can always drop it later.
Committed d7313cc and pushed to 10.1.x. Thanks!
- ๐ฆ๐บAustralia kim.pepper ๐โโ๏ธ๐ฆ๐บSydney, Australia
Created ๐ Create span for database execution Fixed for OpenTelemetry.
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
Filed โจ Add transaction-related events to the Database API Needs work for follow-up.
- ๐บ๐ธUnited States mfb San Francisco
Is enabling logging the only way to automatically enable events on all new connections? (If so, ideally we could make it easier to enable events without logging.)
Database::openConnection() has
if (!empty(self::$logs[$key])) { $new_connection->enableEvents([ StatementExecutionStartEvent::class, StatementExecutionEndEvent::class, ]);
Btw, I noticed a typo in the change record which I'll fix:
Calling code needs to opt-in for event dispatching by calling
::enableStatementEvents(TRUE)
on the databaseConnection
object.should be
Calling code needs to opt-in for event dispatching by calling
::enableEvents(TRUE)
on the databaseConnection
object. Automatically closed - issue fixed for 2 weeks with no activity.