issue_comments

Table actions

5 rows where issue = 275125805 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

author_association 2

issue 1

  • Option to open readonly but not immutable · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
504879834 https://github.com/simonw/datasette/issues/124#issuecomment-504879834 https://api.github.com/repos/simonw/datasette/issues/124 MDEyOklzc3VlQ29tbWVudDUwNDg3OTgzNA== simonw 9599 2019-06-24T06:43:46Z 2019-06-24T06:43:46Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to open readonly but not immutable 275125805  
347236102 https://github.com/simonw/datasette/issues/124#issuecomment-347236102 https://api.github.com/repos/simonw/datasette/issues/124 MDEyOklzc3VlQ29tbWVudDM0NzIzNjEwMg== simonw 9599 2017-11-27T16:24:15Z 2017-11-27T16:24:15Z OWNER

I'd really like to get some benchmarks working so I can see the actual impact of this kind of thing.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to open readonly but not immutable 275125805  
347123991 https://github.com/simonw/datasette/issues/124#issuecomment-347123991 https://api.github.com/repos/simonw/datasette/issues/124 MDEyOklzc3VlQ29tbWVudDM0NzEyMzk5MQ== janimo 50138 2017-11-27T09:25:15Z 2017-11-27T09:25:15Z NONE

That's the only reference to immutable I saw as well, making me think that there may be no perceivable advantages over simply using mode=ro. Since the database is never or seldom updated the change notifications should not impact performance.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to open readonly but not immutable 275125805  
347049888 https://github.com/simonw/datasette/issues/124#issuecomment-347049888 https://api.github.com/repos/simonw/datasette/issues/124 MDEyOklzc3VlQ29tbWVudDM0NzA0OTg4OA== simonw 9599 2017-11-27T00:01:08Z 2017-11-27T00:01:08Z OWNER

https://sqlite.org/c3ref/open.html Is the only documentation I've been able to find of the immutable option:

immutable: The immutable parameter is a boolean query parameter that indicates that the database file is stored on read-only media. When immutable is set, SQLite assumes that the database file cannot be changed, even by a process with higher privilege, and so the database is opened read-only and all locking and change detection is disabled. Caution: Setting the immutable property on a database file that does in fact change can result in incorrect query results and/or SQLITE_CORRUPT errors. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to open readonly but not immutable 275125805  
346987395 https://github.com/simonw/datasette/issues/124#issuecomment-346987395 https://api.github.com/repos/simonw/datasette/issues/124 MDEyOklzc3VlQ29tbWVudDM0Njk4NzM5NQ== janimo 50138 2017-11-26T06:24:08Z 2017-11-26T06:24:08Z NONE

Are there performance gains when using immutable as opposed to read-only? From what I see other processes can still modify the DB when immutable, but there are no change notifications.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to open readonly but not immutable 275125805  

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