home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 924435971

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/datasette/issues/111#issuecomment-924435971 https://api.github.com/repos/simonw/datasette/issues/111 924435971 IC_kwDOBm6k_c43GcYD 9599 2021-09-21T22:29:15Z 2021-09-21T22:29:49Z OWNER

So this is a metadata key called updated which can be applied at the table, database or instance level. It is represented as a .isoformat() timestamp.

Question: should I support just the date - yyyy-mm-dd - in addition to the datetime?

I think so. I can easily imagine situations where the exact time of day that a change was made hasn't been recorded, but the overall date is known.

But in that case, should the updated key sometimes be yyyy-mm-dd and sometimes be the full isoformat datetime? Or should there be an updated_date key that's used for just the date?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
274615452  
Powered by Datasette · Queries took 0.941ms · About: github-to-sqlite