Describe the bug
Description
PostgreSQL is meant to work the same as SQLServer, in that the ScopeType for usage reports is written as Catalog & Schema. This is not currently happening, with the ScopeType value being blank.
Additionally, SQLServer has the scope value (DB and schema) prepended to every queue, while PostgreSQL only has the schema prepended. Making this consistent will assist in processing the usage reports
Expected behavior
ScopeType is set to "Catalog & Schema"
Actual behavior
ScopeType is a blank string
Versions
Please list the version of the relevant packages or applications in which the bug exists.
6.13.0
NOTE: another PostgreSQL report from version 6.7.3 did have the ScopeType set correctly, so either this is a recent bug or it's environment dependent
Steps to reproduce
- Use NServiceBus with a PostgreSQL transport. Have ServiceControl error instance installed
- Generate a usage report
Relevant log output
Additional Information
Workarounds
Possible solutions
Additional information
Describe the bug
Description
PostgreSQL is meant to work the same as SQLServer, in that the ScopeType for usage reports is written as
Catalog & Schema. This is not currently happening, with the ScopeType value being blank.Additionally, SQLServer has the scope value (DB and schema) prepended to every queue, while PostgreSQL only has the schema prepended. Making this consistent will assist in processing the usage reports
Expected behavior
ScopeType is set to "Catalog & Schema"
Actual behavior
ScopeType is a blank string
Versions
Please list the version of the relevant packages or applications in which the bug exists.
6.13.0
NOTE: another PostgreSQL report from version 6.7.3 did have the
ScopeTypeset correctly, so either this is a recent bug or it's environment dependentSteps to reproduce
Relevant log output
Additional Information
Workarounds
Possible solutions
Additional information