issue_comments
2 rows where author_association = "MEMBER", issue = 184722754 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- shallow copies become deep copies when pickling · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
256123953 | https://github.com/pydata/xarray/issues/1058#issuecomment-256123953 | https://api.github.com/repos/pydata/xarray/issues/1058 | MDEyOklzc3VlQ29tbWVudDI1NjEyMzk1Mw== | max-sixty 5635139 | 2016-10-25T18:23:35Z | 2016-10-25T18:23:35Z | MEMBER | @crusaderky right, I see. All those views are in the same pickle object, and so shouldn't be duplicated. That is frustrating. As per @shoyer, the easiest way is to just not have the data in the first place. So not needing indexes at all should solve your case. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
shallow copies become deep copies when pickling 184722754 | |
255801010 | https://github.com/pydata/xarray/issues/1058#issuecomment-255801010 | https://api.github.com/repos/pydata/xarray/issues/1058 | MDEyOklzc3VlQ29tbWVudDI1NTgwMTAxMA== | max-sixty 5635139 | 2016-10-24T17:03:08Z | 2016-10-24T17:03:08Z | MEMBER | If I'm understanding you correctly @crusaderky, I think this is a tough problem, and one much broader than xarray. When pickling something with a reference, do you want to save the object, or the reference? If you pickle the reference, how can you guarantee to have the object available when unpickling? How would you codify the reference (memory location?)? Is that right? Or am I misunderstanding your problem? On this narrow case, I think not having indexes at all should solve this, though |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
shallow copies become deep copies when pickling 184722754 |
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