home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 99847237 and user = 2443309 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • jhamman · 3 ✖

issue 1

  • Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' · 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
131187220 https://github.com/pydata/xarray/pull/523#issuecomment-131187220 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEzMTE4NzIyMA== jhamman 2443309 2015-08-14T17:22:02Z 2015-08-14T17:22:02Z MEMBER

I submitted an feature request over at numpy. I'm going to close this now.

@rabernat - thanks for the PR and keep them coming.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237
131166492 https://github.com/pydata/xarray/pull/523#issuecomment-131166492 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEzMTE2NjQ5Mg== jhamman 2443309 2015-08-14T16:17:10Z 2015-08-14T16:17:10Z MEMBER

Worth? Yes. Any hope to actually get it in there? No...

I think I disagree. There is almost no chance anyone outside of the climate community is going to spend time on this but, if calendar support was added in a responsible way to numpy and pandas, I don't see why they wouldn't be interested. So it will need to come from the climate users community, which IMHO, is under represented in the dev community.

If you don't want open the issue, I will.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237
129101660 https://github.com/pydata/xarray/pull/523#issuecomment-129101660 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEyOTEwMTY2MA== jhamman 2443309 2015-08-09T03:43:09Z 2015-08-09T03:43:09Z MEMBER

I have a few general comments,
1. Can you point me to where in the CF Conventions or UDUNITS the valid time coordinate units defined? 2. We should think about whether or not this fix belongs in xray or netCDF4. I am of the opinion that if the CF Conventions do in fact support the units in question, we should apply this fix in the netCDF package. If they don't, I don't think we wan to support it here either. 3. @shoyer is out for a bit but he will almost certainly want to weigh in on this.

If we end up going this route, you'll want to add some unit tests in test_conventions.py.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237

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 9522.008ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows