home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

9 rows where issue = 753668177 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

  • simonw 8
  • nattaylor 1

author_association 2

  • OWNER 8
  • NONE 1

issue 1

  • GENERATED column support · 9 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
736030599 https://github.com/simonw/datasette/issues/1116#issuecomment-736030599 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNjAzMDU5OQ== simonw 9599 2020-11-30T20:41:41Z 2020-11-30T20:41:41Z OWNER

Here's the problem: https://www.sqlite.org/changes.html#version_3_26_0

2018-12-01 (3.26.0)

  • Added PRAGMA table_xinfo that works just like PRAGMA table_info except that it also shows hidden columns in virtual tables.

CI is running 3.22.0.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
736015487 https://github.com/simonw/datasette/issues/1116#issuecomment-736015487 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNjAxNTQ4Nw== simonw 9599 2020-11-30T20:11:07Z 2020-11-30T20:11:07Z OWNER

Working on this in a pull request: https://github.com/simonw/datasette/pull/1117

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
736014372 https://github.com/simonw/datasette/issues/1116#issuecomment-736014372 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNjAxNDM3Mg== simonw 9599 2020-11-30T20:08:48Z 2020-11-30T20:08:48Z OWNER

Ouch, the tests pass on my laptop but failed in CI: https://github.com/simonw/datasette/actions/runs/392367997

Lots of failures look like this: ERROR: conn=<sqlite3.Connection object at 0x7f44f0494030>, sql = 'select rowid, from facetable order by rowid limit 51', params = {}: near "from": syntax error Note the select rowid, from... - so it looks like invalid SQL queries are being constructed maybe due to mis-detecting columns somehow.

I wonder why it didn't fail on my laptop?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
736010720 https://github.com/simonw/datasette/issues/1116#issuecomment-736010720 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNjAxMDcyMA== simonw 9599 2020-11-30T20:01:53Z 2020-11-30T20:01:53Z OWNER

I'm OK exposing hidden columns, unless someone comes up with a pressing reason not to.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
736005833 https://github.com/simonw/datasette/issues/1116#issuecomment-736005833 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNjAwNTgzMw== nattaylor 2789593 2020-11-30T19:54:39Z 2020-11-30T19:54:39Z NONE

@simonw thanks for investigating so quickly. If it is undesirable to change that hidden behavior, maybe something like this is a suitable workaround: SELECT * FROM pragma_table_xinfo('deeds') where hidden in (0,2); 0|body|TEXT|0||0|0 1|id|INT GENERATED ALWAYS|0||0|2 2|consideration|INT GENERATED ALWAYS|0||0|2

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
736004383 https://github.com/simonw/datasette/issues/1116#issuecomment-736004383 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNjAwNDM4Mw== simonw 9599 2020-11-30T19:51:51Z 2020-11-30T19:51:51Z OWNER

This change will also have an impact on how hidden virtual FTS tables are displayed, since apparently those have some hidden columns: https://latest.datasette.io/fixtures?sql=select+*+from+pragma_table_xinfo%28%27searchable_fts%27%29

| cid | name | type | notnull | dflt_value | pk | hidden | | --- | --- | --- | --- | --- | --- | --- | | 0 | text1 | | 0 | | 0 | 0 | | 1 | text2 | | 0 | | 0 | 0 | | 2 | name with . and spaces | | 0 | | 0 | 0 | | 3 | searchable_fts | | 0 | | 0 | 1 | | 4 | docid | | 0 | | 0 | 1 | | 5 | __langid | | 0 | | 0 | 1 |

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
735995695 https://github.com/simonw/datasette/issues/1116#issuecomment-735995695 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNTk5NTY5NQ== simonw 9599 2020-11-30T19:34:15Z 2020-11-30T19:34:15Z OWNER

Generated column support was added in SQLite 3.31.0, so any unit tests I write for this should use skipIf to only run on that version or later.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
735993935 https://github.com/simonw/datasette/issues/1116#issuecomment-735993935 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNTk5MzkzNQ== simonw 9599 2020-11-30T19:30:44Z 2020-11-30T19:32:15Z OWNER

It looks like PRAGMA table_info skips "hidden" columns: https://www.sqlite.org/pragma.html#pragma_table_info

But PRAGMA table_xinfo does not: https://www.sqlite.org/pragma.html#pragma_table_xinfo

Compare https://latest.datasette.io/fixtures?sql=select++from+pragma_table_info%28%27searchable%27%29 to https://latest.datasette.io/fixtures?sql=select++from+pragma_table_xinfo%28%27searchable%27%29 - the xinfo one has an additional hidden column.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  
735992106 https://github.com/simonw/datasette/issues/1116#issuecomment-735992106 https://api.github.com/repos/simonw/datasette/issues/1116 MDEyOklzc3VlQ29tbWVudDczNTk5MjEwNg== simonw 9599 2020-11-30T19:27:10Z 2020-11-30T19:27:10Z OWNER

I'm treating this as a bug - these columns should definitely be visible in Datasette.

I created my own test database using SQLite from Homebrew like this: /usr/local/Cellar/sqlite/3.33.0/bin/sqlite3 deeds.db << EOF CREATE TABLE deeds ( body TEXT, id INT GENERATED ALWAYS AS (json_extract(body, '$.id')) STORED, consideration INT GENERATED ALWAYS AS (json_extract(body, '$.consideration')) STORED ); INSERT INTO deeds (body) VALUES ('{ "id": 1, "consideration": "This is the consideration" }'); EOF

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
GENERATED column support 753668177  

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 20.325ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows