home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 753668177

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
753668177 MDU6SXNzdWU3NTM2NjgxNzc= 1116 GENERATED column support 2789593 closed 0     9 2020-11-30T17:33:47Z 2020-11-30T21:29:59Z 2020-11-30T21:29:59Z NONE  

I think this is a feature request... perhaps I should just try to contribute it myself, but thought I'd check in case support is planned already.

For a table with the following schema, datasette 0.51.1 doesn't pick up the GENERATED columns and the column list only contains (rowid, body) If I edit the SQL and select the generated columns, it will happily show them.

At first glance it appears that def table_column_details(conn, table): would have to be refactored to use a different methodology to get the columns, since PRAGMA table_info(deeds); returns just 0|body|TEXT|0||0 so maybe it wouldn't be worth it.

CREATE TABLE deeds ( body TEXT, id INT GENERATED ALWAYS AS (json_extract(body, '$.id')) STORED, consideration INT GENERATED ALWAYS AS (json_extract(body, '$.consideration')) STORED );

107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1116/reactions",
    "total_count": 0,
    "+1": 0,
    "-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
  • 9 rows from issue in issue_comments
Powered by Datasette · Queries took 1.471ms · About: github-to-sqlite