Further Examples of Data Prometheus

This is an example of Data Prometheus attempting to re-map a database that already has relationships. The first image was generated using SchemaCrawler, a database mapping tool that was used during the capstone phase of the project. After I began expanding Data Prometheus, I decided to move away from using SchemaCrawler to generate graph images.

Even at this basic stage, Data Prometheus is able to programatically and correctly identify 9 out of 11 relationships in chinook.db. Despite incorrectly identifying two relationships (Customers/SupportRepId -> Employees/EmployeeId and Employees/ReportsTo -> Employees/EmployeeId), the table structure is identical to a database with predefined relationships.

↓

This example is a slightly larger version of the example from my portfolio's main page. This shows the ability of Data Prometheus to determine relationships between multiple different tables, as well as more clearly showing the moonbuggy_users table as the source that the other RecordKey keys are referencing.

↓

An even larger example of the moonbuggy database, this is the database that we were originally given. The previous examples were modified to be clearer and easier to understand.

↓