issue_comments: 688626037

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions issue performed_via_github_app 688626037 MDEyOklzc3VlQ29tbWVudDY4ODYyNjAzNw== 9599 2020-09-08T05:27:07Z 2020-09-08T05:27:07Z MEMBER

A really clever way to do this would be with triggers. The indexer script would add triggers to each of the database tables that it is indexing - each in their own database.

Those triggers would then maintain a _index_queue_ table. This table would record the primary key of rows that are added, modified or deleted. The indexer could then work by reading through the _index_queue_ table, re-indexing (or deleting) just the primary keys listed there, and then emptying the queue once it has finished.

This would add a small amount of overhead to insert/update/delete queries run against the table. My hunch is that the overhead would be miniscule, but I could still allow people to opt-out for tables that are so high traffic that this would matter.

    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
Powered by Datasette · Query took 1.372ms · About: github-to-sqlite