issue_comments

Table actions

4 rows where issue = 1843710170 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

issue 1

  • Query view shouldn't return `columns` · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1671982215 https://github.com/simonw/datasette/issues/2136#issuecomment-1671982215 https://api.github.com/repos/simonw/datasette/issues/2136 IC_kwDOBm6k_c5jqGyH simonw 9599 2023-08-09T19:02:19Z 2023-08-09T19:02:19Z OWNER

I'm going with a bit of a hacky workaround for the moment, until I get a chance to refactor this: - #2137 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Query view shouldn't return `columns` 1843710170  
1671964003 https://github.com/simonw/datasette/issues/2136#issuecomment-1671964003 https://api.github.com/repos/simonw/datasette/issues/2136 IC_kwDOBm6k_c5jqCVj simonw 9599 2023-08-09T18:53:10Z 2023-08-09T18:53:18Z OWNER

I made an initial attempt at this in a branch, but it broke too much other stuff. https://github.com/simonw/datasette/commit/f3944608cc000a2542b4fe9a7a89c866391924f2

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Query view shouldn't return `columns` 1843710170  
1671861623 https://github.com/simonw/datasette/issues/2136#issuecomment-1671861623 https://api.github.com/repos/simonw/datasette/issues/2136 IC_kwDOBm6k_c5jppV3 simonw 9599 2023-08-09T17:34:35Z 2023-08-09T17:34:35Z OWNER

I'll make ?_extra=columns work in: - #2113

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Query view shouldn't return `columns` 1843710170  
1671848664 https://github.com/simonw/datasette/issues/2136#issuecomment-1671848664 https://api.github.com/repos/simonw/datasette/issues/2136 IC_kwDOBm6k_c5jpmLY simonw 9599 2023-08-09T17:24:37Z 2023-08-09T17:24:37Z OWNER

It also bothers me that ok comes first in one but not first in the other - I'd like the order of keys in the JSON to be consistent, even though order isn't meant to mean anything.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Query view shouldn't return `columns` 1843710170  

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