issue_comments
Data license: AGPL · Data source: ACEmulator Project
1 row where issue = 481973678
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 |
---|---|---|---|---|---|---|---|---|---|---|---|
522319579 | https://github.com/ACEmulator/ACE/pull/2245#issuecomment-522319579 | https://api.github.com/repos/ACEmulator/ACE/issues/2245 | MDEyOklzc3VlQ29tbWVudDUyMjMxOTU3OQ== | Mag-nus 10608427 | 2019-08-18T12:52:04Z | 2019-08-18T12:55:06Z | MEMBER | I'm strongly against this kind of separation. It will absolutely lead to an error due to misuse, and you'll end up with guid errors. Even with the current dynamic guid recycling disabled, guid allocation in ACE is no longer an issue. This is trying to solve a problem that no longer exists in ACE, and is allocating items to GUID's that weren't found in retail. The risk here is very high! | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Add StuckGuidAllocator 481973678 |
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]);