issue_comments

Table actions

5 rows where issue = 571805300 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • simonw · 5 ✖

issue 1

  • table.disable_fts() method and "sqlite-utils disable-fts ..." command · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
591769171 https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769171 https://api.github.com/repos/simonw/sqlite-utils/issues/88 MDEyOklzc3VlQ29tbWVudDU5MTc2OTE3MQ== simonw 9599 2020-02-27T04:05:58Z 2020-02-27T04:26:31Z OWNER

Strange - https://www.sqlite.org/lang_droptrigger.html says "Note that triggers are automatically dropped when the associated table is dropped" but that doesn't seem to be true in my experimenting.

UPDATE: no that makes sense - the triggers are on resources which still exists, it was resources_fts that was dropped.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.disable_fts() method and "sqlite-utils disable-fts ..." command 571805300  
591769759 https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769759 https://api.github.com/repos/simonw/sqlite-utils/issues/88 MDEyOklzc3VlQ29tbWVudDU5MTc2OTc1OQ== simonw 9599 2020-02-27T04:08:29Z 2020-02-27T04:08:29Z OWNER

I think the method should be called table.disable_fts() - the opposite of table.enable_fts(...).

There should be a sqlite-utils disable-fts database.db tablename command to match it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.disable_fts() method and "sqlite-utils disable-fts ..." command 571805300  
591769373 https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769373 https://api.github.com/repos/simonw/sqlite-utils/issues/88 MDEyOklzc3VlQ29tbWVudDU5MTc2OTM3Mw== simonw 9599 2020-02-27T04:06:47Z 2020-02-27T04:06:47Z OWNER

Looks like safest option is to loop through those trigger names and run DROP TRIGGER IF EXISTS foo on each one.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.disable_fts() method and "sqlite-utils disable-fts ..." command 571805300  
591769046 https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769046 https://api.github.com/repos/simonw/sqlite-utils/issues/88 MDEyOklzc3VlQ29tbWVudDU5MTc2OTA0Ng== simonw 9599 2020-02-27T04:05:15Z 2020-02-27T04:05:15Z OWNER

I can reliably get the list of triggers to delete from select name from sqlite_master where type = 'trigger' and tbl_name = 'resources';

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.disable_fts() method and "sqlite-utils disable-fts ..." command 571805300  
591768604 https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591768604 https://api.github.com/repos/simonw/sqlite-utils/issues/88 MDEyOklzc3VlQ29tbWVudDU5MTc2ODYwNA== simonw 9599 2020-02-27T04:03:03Z 2020-02-27T04:03:03Z OWNER

drop table resources_fts drops the FTS table and the other ones that it created (resources_fts_data, resources_fts_idx, resources_fts_docsize, resources_fts_config) - but keeps the triggers.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.disable_fts() method and "sqlite-utils disable-fts ..." command 571805300  

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