OOPS SQL Statement Logs should include database and user
Bug #354035 reported by
Francis J. Lacoste
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Stuart Bishop | ||
Bug Description
Now that we are using multiple stores and multiple connections in a request, the SQL statement logs that gets dumped into any OOPS should include the database and user (connection info) used for each statement.
An example where this would be useful is in diagnosing permission problems like shown in OOPS-1187D1961.
Related branches
lp:~stub/launchpad/bug-354035
- Diogo Matsubara (community): Approve (qa)
- Gavin Panella (community): Approve (code)
- Diff: None lines
| Changed in launchpad-foundations: | |
| importance: | Undecided → High |
| milestone: | none → 2.2.4 |
| status: | New → Triaged |
| Changed in launchpad-foundations: | |
| milestone: | 2.2.4 → 2.2.6 |
| Changed in launchpad-foundations: | |
| milestone: | 2.2.6 → 2.2.7 |
| Changed in launchpad-foundations: | |
| assignee: | nobody → Stuart Bishop (stub) |
| Changed in launchpad-foundations: | |
| milestone: | 2.2.7 → 2.2.8 |
| Changed in launchpad-foundations: | |
| status: | Triaged → In Progress |
| Changed in oops-tools: | |
| assignee: | nobody → Diogo Matsubara (matsubara) |
| importance: | Undecided → High |
| milestone: | none → 2.2.8 |
| status: | New → Fix Released |
Revision history for this message
| Diogo Matsubara (matsubara) wrote Bug fixed by a commit | #1 |
| Changed in launchpad-foundations: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in devel r9044.