issue_comments
1 row where issue = 1266308714 and user = 4502 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Datatype for a 'shape specification' of a Dataset / DataArray · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1183534601 | https://github.com/pydata/xarray/issues/6680#issuecomment-1183534601 | https://api.github.com/repos/pydata/xarray/issues/6680 | IC_kwDOAMm_X85Gi04J | mjwillson 4502 | 2022-07-13T18:17:05Z | 2022-07-13T18:17:05Z | NONE | Thanks, that looks interesting, although sounds like it's addressing a slightly different problem; I'm not so much interested in validation of external inputs, more just in having some basic datatypes that can be used to specify dims/shape/coords as templates for DataArray / Datasets internally within my codebase. Some things I'm looking for but don't appear to be supported:
* Support for specifying coords
* Feels to me that it would make sense to have these basic datatypes inside xarray, perhaps with something like xarray-schema providing extra validation helpers etc on top of them? But just my 2 cents :) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Datatype for a 'shape specification' of a Dataset / DataArray 1266308714 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1