Define a table for the HWDB for structured storage of the DMI data and lspci output

Bug #327147 reported by Abel Deuring
2
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.

Abel Deuring (adeuring)
Changed in malone:
status: New → Triaged
Abel Deuring (adeuring)
description: updated
Abel Deuring (adeuring)
Changed in malone:
assignee: nobody → adeuring
status: Triaged → In Progress
Abel Deuring (adeuring)
Changed in malone:
importance: Undecided → High
Curtis Hovey (sinzui)
Changed in malone:
status: In Progress → Triaged
assignee: Abel Deuring (adeuring) → nobody
Revision history for this message
Robert Collins (lifeless) wrote :

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.

Changed in launchpad:
importance: High → Low
Revision history for this message
Colin Watson (cjwatson) wrote :

We've removed the hardware database, so this is no longer applicable.

Changed in launchpad:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.