issue_comments
Data license: AGPL · Data source: ACEmulator Project
4 rows where user = 51647865
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions, issue, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
500415322 | https://github.com/ACEmulator/ACE/pull/1985#issuecomment-500415322 | https://api.github.com/repos/ACEmulator/ACE/issues/1985 | MDEyOklzc3VlQ29tbWVudDUwMDQxNTMyMg== | TheKnobGoblin 51647865 | 2019-06-10T13:24:20Z | 2019-06-10T13:24:20Z | NONE | > See my comments in this PR regarding storing IP addresses in a database: #1471 I strongly disagree with storing the IP fields in VARBINARY. I've never seen it used that way and it majorly over complicates things. VARCHAR works perfectly fine for any IP address and it's used to store an IP 99% of the time for servers. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Add Creation/LastLogin IP/DateTime 454022098 | |
500433806 | https://github.com/ACEmulator/ACE/pull/1985#issuecomment-500433806 | https://api.github.com/repos/ACEmulator/ACE/issues/1985 | MDEyOklzc3VlQ29tbWVudDUwMDQzMzgwNg== | TheKnobGoblin 51647865 | 2019-06-10T14:19:19Z | 2019-06-10T14:19:19Z | NONE | The use case is that it makes both storing and reading the IP address easier. The performance gain from VARBINARY is negligible and makes the IP address unreadable when you want to simply look at the account table and see which IP belongs to which account. I think it's silly to block this PR because it's not modern enough for you. Keeping things simple is the best approach, especially for a community driven open source emulator project. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Add Creation/LastLogin IP/DateTime 454022098 | |
552712772 | https://github.com/ACEmulator/ACE/pull/2412#issuecomment-552712772 | https://api.github.com/repos/ACEmulator/ACE/issues/2412 | MDEyOklzc3VlQ29tbWVudDU1MjcxMjc3Mg== | TheKnobGoblin 51647865 | 2019-11-12T03:01:53Z | 2019-11-12T03:01:53Z | NONE | It works, you need to run the sql so that existing account levels are converted to the new ones. Also you can't simply update the rows in the accesslevel table due to one of them being a primary key. I see nothing wrong with dropping this table and remaking it but your call. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Added NoAccess as an AccessLevel 521293376 | |
552914003 | https://github.com/ACEmulator/ACE/pull/2412#issuecomment-552914003 | https://api.github.com/repos/ACEmulator/ACE/issues/2412 | MDEyOklzc3VlQ29tbWVudDU1MjkxNDAwMw== | TheKnobGoblin 51647865 | 2019-11-12T14:22:06Z | 2019-11-12T14:22:06Z | NONE | I've tested this and it works perfectly. You're defeating the entire purpose of mandatory sql updates when they're made. Server owners always need to install them. Also who cares about whether the sql is on one line or not? It's just a simple update script that will be eventually moved to the base anyway. Anyway, I'll keep this to myself and make sure not to contribute to this project anymore. | {"total_count": 1, "+1": 0, "-1": 1, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Added NoAccess as an AccessLevel 521293376 |
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]);