issue_comments: 813115414

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 813115414 MDEyOklzc3VlQ29tbWVudDgxMzExNTQxNA== 9599 2021-04-04T23:23:34Z 2021-04-04T23:23:34Z OWNER

The other approach I considered for this was to have my own SQL query parser running in Python, which could pick apart a complex query and figure out which column was sourced from which table. I dropped this idea because it felt that the moment select * came into play a pure parsing approach wouldn't work - I'd need knowledge of the schema in order to resolve the *.

A Python parser approach might be good enough to handle a subset of queries - those that don't use select * for example - and maybe that would be worth shipping? The feature doesn't have to be perfect for it to be useful.

    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0