home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "OWNER" and issue = 735663855 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

  • table.search() improvements plus sqlite-utils search command · 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
723148906 https://github.com/simonw/sqlite-utils/pull/195#issuecomment-723148906 https://api.github.com/repos/simonw/sqlite-utils/issues/195 MDEyOklzc3VlQ29tbWVudDcyMzE0ODkwNg== simonw 9599 2020-11-06T15:43:51Z 2020-11-06T15:43:51Z OWNER

Thanks to #198 (introducing a rank_bm25() custom function for FTS4) this feature will be able to offer relevance search for both FTS5 AND FTS4 tables.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
table.search() improvements plus sqlite-utils search command 735663855  
722542895 https://github.com/simonw/sqlite-utils/pull/195#issuecomment-722542895 https://api.github.com/repos/simonw/sqlite-utils/issues/195 MDEyOklzc3VlQ29tbWVudDcyMjU0Mjg5NQ== simonw 9599 2020-11-05T18:01:33Z 2020-11-05T18:01:33Z OWNER

Latest test failure: 114 -> assert [("racoons are biting trash pandas", "USA", "bar")] == table.search( 115 "bite", order="rowid" 116 ) 117 118 119 def test_optimize_fts(fresh_db): (Pdb) table.search("bite") [(2, 'racoons are biting trash pandas', 'USA', 'bar', -9.641434262948206e-07)] The problem here is that the table.search() method now behaves differently for FTS4 v.s. FTS5 tables.

With FTS4 you get back just the table columns.

With FTS5 you also get back the rowid as the first column and the rank score as the last column.

This is weird. It also makes me question whether having .search() return a list of tuples is the right API design.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
table.search() improvements plus sqlite-utils search command 735663855  
721397665 https://github.com/simonw/sqlite-utils/pull/195#issuecomment-721397665 https://api.github.com/repos/simonw/sqlite-utils/issues/195 MDEyOklzc3VlQ29tbWVudDcyMTM5NzY2NQ== simonw 9599 2020-11-03T22:02:57Z 2020-11-03T22:02:57Z OWNER

Documentation so far: https://github.com/simonw/sqlite-utils/blob/6cadc6103ff1ba58c6409ce7fba74259e72965d9/docs/cli.rst#executing-searches

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
table.search() improvements plus sqlite-utils search command 735663855  

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]);
Powered by Datasette · Queries took 17.492ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows