issue_comments
Data license: AGPL · Data source: ACEmulator Project
1 row where issue = 225352372
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
298311332 | https://github.com/ACEmulator/ACE/pull/309#issuecomment-298311332 | https://api.github.com/repos/ACEmulator/ACE/issues/309 | MDEyOklzc3VlQ29tbWVudDI5ODMxMTMzMg== | Forbiddenz 25387933 | 2017-05-01T09:36:18Z | 2017-05-01T09:36:18Z | CONTRIBUTOR | I would keep it separated but you may need to see why the the ref issue is happening and if it all that ref is still needed. Logically I say cell data would not have any ref at all and would be ref by ace, and other classes. The circular ref occurres when the ace ref points to cell and the cell ref points to ace. That is poor ok code design so you got to make sure through proper project layout and code design that you only use the ref project as a ref project and not try to interconnect the too. Hope that helps a little | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Landblocks 225352372 |
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]);