Define a table for the HWDB for structured storage of the DMI data and lspci output
Bug #327147 reported by
Abel Deuring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Won't Fix
|
Low
|
Unassigned |
Bug Description
The DMI data consists of tuples of the form (handle, attribute, value); the HWDB should provide a table that stores this data in a structued, searchable way.
Having such a fine-structed storage model for the lspci ouput is not that important, but we should consider to store the entire text output in a SQL table column, because:
(1) otherwise, we would have to extract it from the Librarian file each time somebody wants to look at the data
(2) we already had discussion if old data should be removed from librarian, so we may omit the raw HWDB submission data at some time.
Changed in malone: | |
status: | New → Triaged |
description: | updated |
Changed in malone: | |
assignee: | nobody → adeuring |
status: | Triaged → In Progress |
Changed in malone: | |
importance: | Undecided → High |
Changed in malone: | |
status: | In Progress → Triaged |
assignee: | Abel Deuring (adeuring) → nobody |
To post a comment you must log in.
We're not currently working on this. Patches appreciated. However most of this is being done in the results tracker now, so possibly LP core should just drop the tables.