✨ feat: view, filter and group dml by caller namespace #604
Description
Is your feature request related to a problem?
Although dml is in the default namespace by definition it would be great to view, filter and group on the namespace of the caller which executed the DML.
For example pkg1 does dml on account records. There exists triggers for pkg1, pkg2 and pkg3.
Each trigger in each package has an associated CODE_UNIT and we have associate the correct namespace and therefore time to these. However the DML_BEGIN event is the parent of the CODE_UNIT events, it is called by pkg1 and has child CODE_UNIT events for pkg1, pkg2 and pkg3 but any additional cost no directly in the code_unit event for the package triggers is a cost and time spend by the platform (system or default).
The caller is pkg1 but the DML_BEGIN is System / default.
When is comes to grouping / filtering what we are probably interested in here is the namespace of the pkg that caused the DML, but I think it is still correct to have the namespace of DML_BEGIN as default/ system.
Describe the solution you'd like
View, filter and group dml rows on the db tab by the callers namespace. Needs to be clear this is the callers namespace and not the dmls namespace.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered
Additional context
Add any other context or screenshots about the feature request here