issue_comments

Table actions

2 rows where user = 119974 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • coleifer · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
392828475 https://github.com/simonw/datasette/issues/191#issuecomment-392828475 https://api.github.com/repos/simonw/datasette/issues/191 MDEyOklzc3VlQ29tbWVudDM5MjgyODQ3NQ== coleifer 119974 2018-05-29T15:50:18Z 2018-05-29T15:50:18Z NONE

Python standard-library SQLite dynamically links against the system sqlite3. So presumably you installed a more up-to-date sqlite3 somewhere on your LD_LIBRARY_PATH.

To compile a statically-linked pysqlite you need to include an amalgamation in the project root when building the extension. Read the relevant setup.py.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Figure out how to bundle a more up-to-date SQLite 310533258  
381602005 https://github.com/simonw/datasette/issues/191#issuecomment-381602005 https://api.github.com/repos/simonw/datasette/issues/191 MDEyOklzc3VlQ29tbWVudDM4MTYwMjAwNQ== coleifer 119974 2018-04-16T13:37:32Z 2018-04-16T13:37:32Z NONE

I don't think it should be too difficult... you can look at what @ghaering did with pysqlite (and similarly what I copied for pysqlite3). You would theoretically take an amalgamation build of Sqlite (all code in a single .c and .h file). The AmalgamationLibSqliteBuilder class detects the presence of this amalgamated source file and builds a statically-linked pysqlite.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Figure out how to bundle a more up-to-date SQLite 310533258  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);