issue_comments

Table actions

4 rows where issue = 443038584 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

issue 1

  • Decide what to do about /-/inspect · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
506797736 https://github.com/simonw/datasette/issues/465#issuecomment-506797736 https://api.github.com/repos/simonw/datasette/issues/465 MDEyOklzc3VlQ29tbWVudDUwNjc5NzczNg== simonw 9599 2019-06-28T16:34:33Z 2019-06-28T16:34:33Z OWNER

I'm closing this because #531 counts as a decision.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Decide what to do about /-/inspect 443038584  
506797086 https://github.com/simonw/datasette/issues/465#issuecomment-506797086 https://api.github.com/repos/simonw/datasette/issues/465 MDEyOklzc3VlQ29tbWVudDUwNjc5NzA4Ng== simonw 9599 2019-06-28T16:32:33Z 2019-06-28T16:32:33Z OWNER

Next step:

  • [ ] build /database/-/inspect which shows tables, columns, column types and foreign keys

It won't show table counts. Or maybe it will include them optionally but only for -I databases, in a special area of the JSON reserved for immutable-only inspect details.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Decide what to do about /-/inspect 443038584  
492904704 https://github.com/simonw/datasette/issues/465#issuecomment-492904704 https://api.github.com/repos/simonw/datasette/issues/465 MDEyOklzc3VlQ29tbWVudDQ5MjkwNDcwNA== simonw 9599 2019-05-16T03:41:27Z 2019-05-16T03:41:27Z OWNER

The main use-case for this endpoint now is going to be Datasette Registry (which really needs some more love).

That tool needs to be able to query a Datasette and find out:

  • What tables are available
  • What their columns are
  • Ideally, their row counts

A single /-/inspect call is no good here because with Datasette Library #417 I'm going to be encouraging MUCH larger Datasette instances, potentially with hundreds of attached databases and thousands of attached tables. So pagination will be essential.

Maybe a smarter approach will be the older idea of having a separate inspect for each database (and maybe each table):

  • /mydatabase/-/inspect
  • /mydatabase/mytable/-/inspect

Either way, I'm going to decouple this from milestone 0.28.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Decide what to do about /-/inspect 443038584  
491545872 https://github.com/simonw/datasette/issues/465#issuecomment-491545872 https://api.github.com/repos/simonw/datasette/issues/465 MDEyOklzc3VlQ29tbWVudDQ5MTU0NTg3Mg== simonw 9599 2019-05-11T21:40:07Z 2019-05-11T21:40:07Z OWNER

I split this out from #462

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Decide what to do about /-/inspect 443038584  

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