Breakpad/Design/Database: Difference between revisions

Breakpad/Design/Database (view source)

226 bytes added , 30 March 2007

no edit summary

3,035

edits

@@ Line 3: / Line 3: @@
 = Breakpad Database =
-* Use MySQL, like everything else (we should revisit this, as it may NOT be the right choice --morgamic)
+* PostgreSQL 8.1 or higher will be used because it offers things that MySQL does not have
-** Would we need to make use of stored procedures or views?
+** Arguably better performance for larger data sets
-** Would we need to do any sort of partitioning?
+** More precise datatypes
-** Does MySQL scale as well as PgSQL for arbitrarily large data sets?
+** Potential for partitioning if we need to scale the database in the future, which will likely happen if we plan on keeping more than 3 months worth of data
-** Any other reason why MySQL would hang us up (table type/storage engine problems)?
+** Long-standing support for stored procedures (which can be in Python :D)
+** Views for databases that are heavily normalized
 * Define schema that works well with current query/reporting needs
+** Need to define metadata that we absolutely have to have
+** Other information and common reports that any crash reporting system would have
 ** [need to dig up all common queries - jay]
 * The schema now accounts for the following kinds of information