issue_comments
3 rows where issue = 359240638 and user = 514522 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Updated text for indexing page · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
422368970 | https://github.com/pydata/xarray/issues/2410#issuecomment-422368970 | https://api.github.com/repos/pydata/xarray/issues/2410 | MDEyOklzc3VlQ29tbWVudDQyMjM2ODk3MA== | horta 514522 | 2018-09-18T12:17:06Z | 2018-09-18T12:17:06Z | CONTRIBUTOR | I will first try to have both together. I'm well aware that learning by examples (that is true for me at least and apparently to most of people: tldr library), so at first I will try to combine all in one page:
I prefer starting with 2 and 3 for me to actually understand xarray... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Updated text for indexing page 359240638 | |
421998857 | https://github.com/pydata/xarray/issues/2410#issuecomment-421998857 | https://api.github.com/repos/pydata/xarray/issues/2410 | MDEyOklzc3VlQ29tbWVudDQyMTk5ODg1Nw== | horta 514522 | 2018-09-17T12:40:52Z | 2018-09-17T12:40:52Z | CONTRIBUTOR | I have updated mainly the Indexing and selection data section. I'm proposing an indexing notation using Xarray definitionA data array
Each data array dimension has an unique
A data array can have zero or more coordinates, represented by a dict-like A coordinate can have zero or more dimensions associated with. A dimension data array is a unidimensional coordinate data array associated with one, and only one, dimension having the same name as the coordinate data array itself. A dimension data array has always one, and only one, coordinate. That coordinate has again a dimension data array associated with: ```python
The above data array
Coordinate data arrays are meant to provide labels to array positions, allowing for convenient access to array elements: ```python
Note that there is no asterisk symbol for coordinate Indexing and selecting dataThere are four different but equally powerful ways of selecting data from a data array. They differ only on the type of dimension and index lookups: position-based lookup and label-based lookup:
A dimension position-based lookup is determined by the used position in the index operator: A dimension label-based lookup is determined by the provided dimension name: [1] An index label is any Numpy data type object. Consider the following data array: ```python
The expressions
Formal indexing definitionLet Let
For each
Consider
The positions |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Updated text for indexing page 359240638 | |
420446944 | https://github.com/pydata/xarray/issues/2410#issuecomment-420446944 | https://api.github.com/repos/pydata/xarray/issues/2410 | MDEyOklzc3VlQ29tbWVudDQyMDQ0Njk0NA== | horta 514522 | 2018-09-11T22:25:23Z | 2018-09-11T22:25:23Z | CONTRIBUTOR | Thanks guys! Just to make sure, this is a work in progress. i realise that I made some wrong assumptions, and there are more to add into it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Updated text for indexing page 359240638 |
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