Improve naming of database tables/fields

[Sergio Durigan Junior]

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.

[Frank Ch. Eigler (fche)]

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.

[Sergio Durigan Junior (sergiodj)]

Hey Frank,

Thanks for the comment. Maybe I should have mentioned earlier, but this bug is about the ubuntu-debuginfod project and the database it uses, *not* about upstream!

*But*, since you commented and seem open to adopting the same normalization for upstream's database, I'll see about filing a bug there as well :-).