issue_comments

Table actions

5 rows where author_association = "OWNER", issue = 737153927 and user = 9599 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

  • simonw · 5 ✖

issue 1

  • Rethink how table.search() method works · 5 ✖

author_association 1

  • OWNER · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
723365651 https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723365651 https://api.github.com/repos/simonw/sqlite-utils/issues/197 MDEyOklzc3VlQ29tbWVudDcyMzM2NTY1MQ== simonw 9599 2020-11-07T01:06:32Z 2020-11-07T01:06:32Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Rethink how table.search() method works 737153927  
723360842 https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723360842 https://api.github.com/repos/simonw/sqlite-utils/issues/197 MDEyOklzc3VlQ29tbWVudDcyMzM2MDg0Mg== simonw 9599 2020-11-07T00:40:55Z 2020-11-07T00:40:55Z OWNER

The order= parameter should be called order_by for consistency with this: python for row in db["dogs"].rows_where("age > 1", order_by="age"):

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Rethink how table.search() method works 737153927  
723230732 https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723230732 https://api.github.com/repos/simonw/sqlite-utils/issues/197 MDEyOklzc3VlQ29tbWVudDcyMzIzMDczMg== simonw 9599 2020-11-06T18:24:29Z 2020-11-06T18:24:29Z OWNER

Still need to update docs.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Rethink how table.search() method works 737153927  
723148310 https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723148310 https://api.github.com/repos/simonw/sqlite-utils/issues/197 MDEyOklzc3VlQ29tbWVudDcyMzE0ODMxMA== simonw 9599 2020-11-06T15:42:43Z 2020-11-06T15:42:43Z OWNER

Having .search() return tuples when .rows_where() returns dictionaries just feels like bad API design to me - it's inconsistent. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Rethink how table.search() method works 737153927  
722545442 https://github.com/simonw/sqlite-utils/issues/197#issuecomment-722545442 https://api.github.com/repos/simonw/sqlite-utils/issues/197 MDEyOklzc3VlQ29tbWVudDcyMjU0NTQ0Mg== simonw 9599 2020-11-05T18:05:33Z 2020-11-05T18:05:33Z OWNER

This is likely to result in a 3.0 release due to a backwards-incompatible change to the current .search() method - #194

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Rethink how table.search() method works 737153927  

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