home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

6 rows where author_association = "OWNER" and "updated_at" is on date 2021-07-08 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 2

  • "searchmode": "raw" in table metadata 5
  • Mechanism for ranking results from SQLite full-text search 1

user 1

  • simonw 6

author_association 1

  • OWNER · 6 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
876620095 https://github.com/simonw/datasette/issues/1389#issuecomment-876620095 https://api.github.com/repos/simonw/datasette/issues/1389 MDEyOklzc3VlQ29tbWVudDg3NjYyMDA5NQ== simonw 9599 2021-07-08T17:35:09Z 2021-07-08T17:35:09Z OWNER

Also came up here: https://github.com/simonw/datasette/issues/268#issuecomment-876616414

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
"searchmode": "raw" in table metadata 940077168  
876619531 https://github.com/simonw/datasette/issues/1389#issuecomment-876619531 https://api.github.com/repos/simonw/datasette/issues/1389 MDEyOklzc3VlQ29tbWVudDg3NjYxOTUzMQ== simonw 9599 2021-07-08T17:34:16Z 2021-07-08T17:34:16Z OWNER

If I implement this I'll also set it up so ?_searchmode=default can be used to over-ride that and go back to the default behaviour.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
"searchmode": "raw" in table metadata 940077168  
876619271 https://github.com/simonw/datasette/issues/1389#issuecomment-876619271 https://api.github.com/repos/simonw/datasette/issues/1389 MDEyOklzc3VlQ29tbWVudDg3NjYxOTI3MQ== simonw 9599 2021-07-08T17:33:49Z 2021-07-08T17:33:49Z OWNER

Relevant code: https://github.com/simonw/datasette/blob/d23a2671386187f61872b9f6b58e0f80ac61f8fe/datasette/views/table.py#L491-L498

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
"searchmode": "raw" in table metadata 940077168  
876618847 https://github.com/simonw/datasette/issues/1389#issuecomment-876618847 https://api.github.com/repos/simonw/datasette/issues/1389 MDEyOklzc3VlQ29tbWVudDg3NjYxODg0Nw== simonw 9599 2021-07-08T17:33:08Z 2021-07-08T17:33:08Z OWNER

Relevant documentation: https://docs.datasette.io/en/0.57.1/full_text_search.html#advanced-sqlite-search-queries

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
"searchmode": "raw" in table metadata 940077168  
876618582 https://github.com/simonw/datasette/issues/1389#issuecomment-876618582 https://api.github.com/repos/simonw/datasette/issues/1389 MDEyOklzc3VlQ29tbWVudDg3NjYxODU4Mg== simonw 9599 2021-07-08T17:32:40Z 2021-07-08T17:32:40Z OWNER

This makes sense to me since other useful querystring arguments like this can be set as defaults in the metadata.json configuration.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
"searchmode": "raw" in table metadata 940077168  
876616414 https://github.com/simonw/datasette/issues/268#issuecomment-876616414 https://api.github.com/repos/simonw/datasette/issues/268 MDEyOklzc3VlQ29tbWVudDg3NjYxNjQxNA== simonw 9599 2021-07-08T17:29:04Z 2021-07-08T17:29:04Z OWNER

I had setup a full text search on my instance of Datasette for title data for our public library, and was noticing that some of the features of the SQLite FTS weren't working as expected ... and maybe the issue is in the escape_fts() function

That's a deliberate feature (albeit controversial, see #759) - part of the main problem here is that it's easy to construct a SQLite full-text search string which results in a database error. This is a bad user-experience!

You can opt-in to raw SQL queries by appending ?_searchmode=raw to the page, see https://docs.datasette.io/en/stable/full_text_search.html#advanced-sqlite-search-queries

But maybe there should be an option for turning that on by default without needing the query string?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Mechanism for ranking results from SQLite full-text search 323718842  

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 487.798ms · About: github-to-sqlite