Return to Answer

The Schema Visualized The Entity Relationship Diagram (ERD) above was constructed using the data found in the information_schema.columns table. (Thank you to ashleedawg for paring the table down to its bare essentials).

All the table, column and key information was compiled into a SQL script using python3. The results were cross validated with the accepted answer above and the few idiosyncratic foreign key formations left over were hardcoded in at the end.)

The ERD was then reverse engineered using dbschema.

Please find the script and other related files in my GitHub repository.

The interactive HTML version of the ERD is posted up here: https://sedeschema.github.io/

The Schema Visualized The Entity Relationship Diagram (ERD) above was constructed using the data found in the information_schema.columns table. (Thank you to ashleedawg for paring the table down to its bare essentials).

All the table, column and key information were compiled into a SQL script using python3. The results were cross validated with the accepted answer above, and the few idiosyncratic foreign key formations left over were hardcoded in at the end.)

The ERD was then reverse engineered using dbschema.

Please find the script that wrote the SQL and other related files in my GitHub repository.

The interactive HTML version of the ERD is posted here: https://sedeschema.github.io/

The Schema Visualized The Entity Relationship Diagram (ERD) above was constructed using the data found in the information_schema.columns table. (Thank you to ashleedawg for paring the table down to its bare essentials). Python 3 was used to convert all the table, column and key information (pulled from out of SEDE's information_schema.columns table) into a SQL script. (All tables, columns, and foreign key constraints as specified in the accepted answer were included.) The ERD was reverse engineered using dbschema.

Please find the script and other related files in my GitHub repository.

The interactive HTML version of the ERD is posted up here: https://sedeschema.github.io/

The Schema Visualized The Entity Relationship Diagram (ERD) above was constructed using the data found in the information_schema.columns table. (Thank you to ashleedawg for paring the table down to its bare essentials).

All the table, column and key information was compiled into a SQL script using python3. The results were cross validated with the accepted answer above and the few idiosyncratic foreign key formations left over were hardcoded in at the end.) 

The ERD was then reverse engineered using dbschema.

Please find the script and other related files in my GitHub repository.

The interactive HTML version of the ERD is posted up here: https://sedeschema.github.io/

The Schema Visualized The Entity Relationship Diagram (ERD) above was constructed using the data found in the information_schema.columns table. (Thank you to ashleedawg for paring the table down to its bare essentials). Python 3 was used to convert all the table, column and key information into a SQL script. (All tables, columns, and foreign key constraints as specified in the accepted answer were included.) The ERD was reverse engineered using dbschema.

Please find the script and other related files in my GitHub repository.

The interactive HTML version of the ERD is posted up here: https://sedeschema.github.io/

The Schema Visualized The Entity Relationship Diagram (ERD) above was constructed using the data found in the information_schema.columns table. (Thank you to ashleedawg for paring the table down to its bare essentials). Python 3 was used to convert all the table, column and key information (pulled from out of SEDE's information_schema.columns table) into a SQL script. (All tables, columns, and foreign key constraints as specified in the accepted answer were included.) The ERD was reverse engineered using dbschema.

Please find the script and other related files in my GitHub repository.

The interactive HTML version of the ERD is posted up here: https://sedeschema.github.io/