issue_comments: 501539452

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
https://github.com/simonw/sqlite-utils/issues/26#issuecomment-501539452 https://api.github.com/repos/simonw/sqlite-utils/issues/26 501539452 MDEyOklzc3VlQ29tbWVudDUwMTUzOTQ1Mg== 9599 2019-06-13T03:59:32Z 2019-06-13T03:59:32Z OWNER

Another complexity from the https://api.github.com/repos/simonw/datasette/pulls example:

We don't actually want head and base to be pulled out into a separate table. Our ideal table design would probably look something like this:

  • url: ...
  • id: 285698310
  • ...
  • user_id: 9599 -> refs users
  • head_label: simonw:travis-38dev
  • head_ref: travis-38dev
  • head_sha: f274f9004302c5ca75ce89d0abfd648457957e31
  • head_user_id: 9599 -> refs users
  • head_repo_id: 107914493 -> refs repos
  • base_label: simonw:master
  • base_ref: master
  • base_sha: 5e8fbf7f6fbc0b63d0479da3806dd9ccd6aaa945
  • base_user_id: 9599 -> refs users
  • base_repo_id: 107914493 -> refs repos

So the nested head and base sections here, instead of being extracted into another table, were flattened into their own columns.

So perhaps we need a flatten-nested-into-columns mechanism which can be used in conjunction with a extract-to-tables mechanism.

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