Skip to content
This repository was archived by the owner on Oct 21, 2022. It is now read-only.
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions sql_schema/create_table.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
CREATE TABLE self_compatibility_status (install_name VARCHAR(200), status VARCHAR(20), py_version VARCHAR(1), timestamp TIMESTAMP, details TEXT, PRIMARY KEY (install_name, py_version));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like, in the production table, the timestamp is auto-updating?


CREATE TABLE pairwise_compatibility_status (install_name_lower VARCHAR(200), install_name_higher VARCHAR(200), status VARCHAR(20), py_version VARCHAR(1), timestamp TIMESTAMP, details TEXT, PRIMARY KEY (install_name_lower, install_name_higher, py_version));

CREATE TABLE release_time_for_dependencies (install_name VARCHAR(200), dep_name VARCHAR(200), installed_version VARCHAR(50), installed_version_time DATETIME, latest_version VARCHAR(50), latest_version_time DATETIME, is_latest BOOLEAN, timestamp TIMESTAMP, PRIMARY KEY (install_name, dep_name));