issue_comments

Table actions

3 rows where issue = 907642546 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • simonw · 3 ✖

issue 1

  • Supporting additional output formats, like GeoJSON · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
853567861 https://github.com/simonw/sqlite-utils/issues/264#issuecomment-853567861 https://api.github.com/repos/simonw/sqlite-utils/issues/264 MDEyOklzc3VlQ29tbWVudDg1MzU2Nzg2MQ== simonw 9599 2021-06-03T05:12:21Z 2021-06-03T05:12:21Z OWNER

I think this is more likely to happen in Datasette than in sqlite-utils - see https://github.com/simonw/datasette/issues/1356 for thoughts on this.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Supporting additional output formats, like GeoJSON 907642546  
853558741 https://github.com/simonw/sqlite-utils/issues/264#issuecomment-853558741 https://api.github.com/repos/simonw/sqlite-utils/issues/264 MDEyOklzc3VlQ29tbWVudDg1MzU1ODc0MQ== simonw 9599 2021-06-03T04:47:19Z 2021-06-03T04:47:19Z OWNER

This inspired me to re-examine how --get works, hence this issue: https://github.com/simonw/datasette/issues/1355

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Supporting additional output formats, like GeoJSON 907642546  
853553754 https://github.com/simonw/sqlite-utils/issues/264#issuecomment-853553754 https://api.github.com/repos/simonw/sqlite-utils/issues/264 MDEyOklzc3VlQ29tbWVudDg1MzU1Mzc1NA== simonw 9599 2021-06-03T04:32:42Z 2021-06-03T04:36:36Z OWNER

This is a really interesting thought. I've so far resisted the temptation to add plugins to sqlite-utils, partly to avoid overlap with Datasette - but I'm open to discussing it.

There's actually a way for you to do what you're describing using datasette on the command-line, though it's a little obscure - also Datasette doesn't yet have a GeoJSON output extension, though it really should have one.

Here's an example using datasette-yaml:

datasette /tmp/covid.db --get='/covid/ny_times_us_counties.yaml' - rowid: 1 date: '2020-01-21' county: Snohomish state: Washington fips: 53061 cases: 1 deaths: 0 - rowid: 2 date: '2020-01-22' county: Snohomish state: Washington fips: 53061 cases: 1 deaths: 0 It even works with arbitrary SQL queries, though you might have to apply URL encoding to the --get string (this seems to work though): datasette /tmp/covid.db --get='/covid.yaml?sql=select * from ny_times_us_counties limit 2' - date: '2020-01-21' county: Snohomish state: Washington fips: 53061 cases: 1 deaths: 0 - date: '2020-01-22' county: Snohomish state: Washington fips: 53061 cases: 1 deaths: 0 Here's the documentation for --get: https://docs.datasette.io/en/latest/getting_started.html#datasette-get

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Supporting additional output formats, like GeoJSON 907642546  

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]);