home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 1170497629

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
1170497629 I_kwDOBm6k_c5FxGBd 1662 [feature request] Publish to fully static website 32609395 closed 0     1 2022-03-16T03:32:28Z 2022-03-19T00:42:23Z 2022-03-19T00:42:23Z NONE  

It seems currently all datasette publish requires a real backend server which is able to query the database and send results back to the frontend. There are a few projects to on-demand download a portion of data from the database from a sqlite lite database url, and present it directly to the user. These methods leverages web assembly under the hood. I think datasette is a perfect use case for this technology. Below are a few examples of querying sqlite database from frontend directly.

  • Using sqlite3 as a notekeeping document graph with automatic reference indexing
  • Hosting SQLite databases on Github Pages - (or any static file hoster) - phiresky's blog
  • Static torrent website with peer-to-peer queries over BitTorrent on 2M records
107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1662/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed

Links from other tables

  • 1 row from issues_id in issues_labels
  • 1 row from issue in issue_comments
Powered by Datasette · Queries took 1.026ms · About: github-to-sqlite