issue_comments

Table actions

3 rows where author_association = "OWNER", issue = 1072435124 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 · 3 ✖

issue 1

  • Optional caching mechanism for table.lookup() · 3 ✖

author_association 1

  • OWNER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
987016019 https://github.com/simonw/sqlite-utils/issues/350#issuecomment-987016019 https://api.github.com/repos/simonw/sqlite-utils/issues/350 IC_kwDOCGYnMM461KtT simonw 9599 2021-12-06T17:56:57Z 2021-12-06T17:56:57Z OWNER

Would be interesting to micro-benchmark this to get an idea for how much of a performance boost it is, since the indexed SQLite lookups used by table.lookup() should be really fast already.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Optional caching mechanism for table.lookup() 1072435124  
987015327 https://github.com/simonw/sqlite-utils/issues/350#issuecomment-987015327 https://api.github.com/repos/simonw/sqlite-utils/issues/350 IC_kwDOCGYnMM461Kif simonw 9599 2021-12-06T17:56:05Z 2021-12-06T17:56:05Z OWNER

Should I implement this remember to apply the optimization in git-history.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Optional caching mechanism for table.lookup() 1072435124  
987015063 https://github.com/simonw/sqlite-utils/issues/350#issuecomment-987015063 https://api.github.com/repos/simonw/sqlite-utils/issues/350 IC_kwDOCGYnMM461KeX simonw 9599 2021-12-06T17:55:42Z 2021-12-06T17:55:42Z OWNER

API could be this: python id = db["columns"].lookup( {"namespace": namespace_id, "name": column}, cache=True ) This could default to a 100 item LRU cache. You could perhaps modify that with cache_size=500 or with cache_size=None to disable the size limit on that cache.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Optional caching mechanism for table.lookup() 1072435124  

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