home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 400678645 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • max-sixty · 3 ✖

issue 1

  • Add create_test_data to public testing API · 3 ✖

author_association 1

  • MEMBER 3
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
456210705 https://github.com/pydata/xarray/pull/2690#issuecomment-456210705 https://api.github.com/repos/pydata/xarray/issues/2690 MDEyOklzc3VlQ29tbWVudDQ1NjIxMDcwNQ== max-sixty 5635139 2019-01-21T22:06:04Z 2019-01-22T15:59:08Z MEMBER

The only other features I could imagine adding would be a coord over multiple dimensions, and a multi-indexed dimension (but potentially we leave the latter out until we're completely confident about the conventions)

Agree on the names!

@TomNicholas if you want to split this up at all lmk

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add create_test_data to public testing API 400678645
456200066 https://github.com/pydata/xarray/pull/2690#issuecomment-456200066 https://api.github.com/repos/pydata/xarray/issues/2690 MDEyOklzc3VlQ29tbWVudDQ1NjIwMDA2Ng== max-sixty 5635139 2019-01-21T21:11:57Z 2019-01-21T21:11:57Z MEMBER

The reason I had liked this was that I'm often creating a dataset manually, either in a repl or as a fixture in a test, and that added an overhead in both time and reduced consistency. I recently started using the tutorial data, but that requires a network connection (and I kept forgetting the name...)

But I can empathize re compatibility issues; I defer to @shoyer on the balance, or whether xarray.testing.dummy_dataset('some_name') would be feasible

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add create_test_data to public testing API 400678645
455599135 https://github.com/pydata/xarray/pull/2690#issuecomment-455599135 https://api.github.com/repos/pydata/xarray/issues/2690 MDEyOklzc3VlQ29tbWVudDQ1NTU5OTEzNQ== max-sixty 5635139 2019-01-18T16:09:40Z 2019-01-18T16:09:40Z MEMBER

it would mean effectively freezing the output of this helper function

We could add a param or version arg so we can make changes in the future, if this is a concern?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add create_test_data to public testing API 400678645

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,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);
Powered by Datasette · Queries took 5683.155ms · About: xarray-datasette