Database design

Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...

Users: Store user information if user accounts are required.

URLs: Store original URLs and their corresponding short URLs.

Clicks: Track clicks on the shortened URLs for analytics.

erDiagram

USER ||--o{ URLs: owns

USER ||--o{ Analytics: views

URLs ||--o{ Clicks: "leads to"

USER {

string id "User ID"

string name "Username"

string email "User's email"

}

URLs {

string id "URL ID"

string original_url "Original URL"

string short_url "Shortened URL"

date created_at "Creation Date"

date expires_at "Expiration Date"

}

Analytics {

string id "Analytics ID"

string user_id "User ID"

string url_id "URL ID"

int total_clicks "Total Clicks"

date last_accessed "Last Accessed Date"

}

Clicks {

string id "Click ID"

string url_id "URL ID"

string visitor_ip "Visitor IP"

string referer "Referer"

date clicked_at "Click Date"

}

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10