Confirmed users
321
edits
Breakpad/Design/Database: Difference between revisions
Jump to navigation
Jump to search
some comments
No edit summary |
(some comments) |
||
| Line 12: | Line 12: | ||
** (Attribute) | ** (Attribute) | ||
* Product | * Product | ||
** Version | |||
** ? | ** ? | ||
** | * Report | ||
** Report ID | |||
== New Questions | == New Questions | ||
| Line 66: | Line 68: | ||
I am not sure if this is the same problem as below -- I'd like to talk more about this in the meeting (this was on this page from before): | I am not sure if this is the same problem as below -- I'd like to talk more about this in the meeting (this was on this page from before): | ||
* Using the same database and schema for the minidump data and also for control over the processing of the minidumps has created problems in the past. when coruption is introduced, database performance problems crop up, or maintenance is required to manage the collection of minidumps, the processing of incoming minidumps is hindered and we start into a downward spiral of compounding problems. We should do some thinking to see if there are ways to improve on the existing design. | * Using the same database and schema for the minidump data and also for control over the processing of the minidumps has created problems in the past. when coruption is introduced, database performance problems crop up, or maintenance is required to manage the collection of minidumps, the processing of incoming minidumps is hindered and we start into a downward spiral of compounding problems. We should do some thinking to see if there are ways to improve on the existing design. | ||
Does Address need to be separated out? How unique is it in our existing crash reports? | |||