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.
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.