issue_comments

Table actions

3 rows where author_association = "OWNER", "created_at" is on date 2023-08-29 and issue = 1870672704 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

issue 1

  • Add new `--internal internal.db` option, deprecate legacy `_internal` database · 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
1696710911 https://github.com/simonw/datasette/pull/2162#issuecomment-1696710911 https://api.github.com/repos/simonw/datasette/issues/2162 IC_kwDOBm6k_c5lIcD_ simonw 9599 2023-08-29T03:23:44Z 2023-08-29T03:23:44Z OWNER

I'm going to merge this so we can see how it feels.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add new `--internal internal.db` option, deprecate legacy `_internal` database 1870672704  
1696709110 https://github.com/simonw/datasette/pull/2162#issuecomment-1696709110 https://api.github.com/repos/simonw/datasette/issues/2162 IC_kwDOBm6k_c5lIbn2 simonw 9599 2023-08-29T03:20:40Z 2023-08-29T03:22:47Z OWNER

However, one important notes about those new core_ tables: If a --internal DB is passed in, that means those core_ tables will persist across multiple Datasette instances. This wasn't the case before, since _internal was always an in-memory database created from scratch.

I'm completely happy for the core_* tables (or datasette_* or some other name) to live in the persisted-to-disk internal.db database, even though they're effectively meant to be an in-memory cache.

I don't think it causes any harm, and it could even be quite useful to have them visible on disk - other applications could read the internal.db database while Datasette itself is running, should they have some weird reason to want to do that!

Having those tables stick around in internal.db after Datasette shuts down could be useful for other debugging activities as well.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add new `--internal internal.db` option, deprecate legacy `_internal` database 1870672704  
1696707458 https://github.com/simonw/datasette/pull/2162#issuecomment-1696707458 https://api.github.com/repos/simonw/datasette/issues/2162 IC_kwDOBm6k_c5lIbOC simonw 9599 2023-08-29T03:17:54Z 2023-08-29T03:17:54Z OWNER

Documentation preview: https://datasette--2162.org.readthedocs.build/en/2162/internals.html#datasette-s-internal-database

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add new `--internal internal.db` option, deprecate legacy `_internal` database 1870672704  

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