ER Diagram

[SahithiKasim]

Create ER diagram of the database schema and do the documentation for the whole database.

[SahithiKasim]

Please check this ER diagram @SantiagoTorres @sbrunswi and tell me the required changes.

[SantiagoTorres]

I think we should split/explode buildinfo_data into different tables:

1. Package table:

   • PackageID (PK)
   • BuildinfoID (i.e., created by)
   • Arch (from buildinfo)
   • Name (from buildinfo)
   • Version (from buildinfo)
   • Type (source/binary)
     2. Source table:
        • SourceID (PK)
        • Name (from Buildinfo, later to cross-check)
        • Version (from buildinfo, later to cross-check)
        • location (where is the source coming from, TBD)
     3. buildinfoTable:
        • BuildinfoID (PK)
        • SourceID (EK, what source was used)
        • deps (list of PackageIDs)

   Does this make sense?

[SahithiKasim]

I didn't understand about BuildinfoID and Type from the Package table. Is PackageID an integer that automatically increments? \ What is SourceID in the Source table?\ Are the BuildinfoID and SourceID in the buildinfo table foreign keys from other tables?

[SantiagoTorres]

Pretty much, the ones labeled as PK are primary keys on each table

[SahithiKasim]

The Updated ER diagram

[SahithiKasim]

Updated in the readme