Improve naming of database tables/fields
Bug #2025390 reported by
Sergio Durigan Junior
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-debuginfod |
Triaged
|
Wishlist
|
Sergio Durigan Junior |
Bug Description
Currently there is no convention for the names we use for database tables and their fields, so we end up with non-uniform cases (like "created_date" in one table and "date" in another), or with field names that don't really match what is stored there (for example, a field named "source" when it in fact stores either a binary package name or a source package name).
It'd be good to revisit these names later.
To post a comment you must log in.
Reasonable concern, but a few practical problems. First, the sqlite schema is not a part of the public interface of debuginfod, so users should not be affected by the current nomenclature inconsistencies. Second, changing schema can be a big deal, because different versions of debuginfod might share the same db file. (The recent filename prefix/suffix splitting basically requires complete reindexing.)
Maybe open an upstream bug, and next time a breaking schema change is require for some reason, we can roll into it some normalization of these field names.