issue_comments
5 rows where issue = 582517965 and "updated_at" is on date 2020-06-05 sorted by created_at
This data as json, CSV (advanced)
Suggested facets: created_at (date)
issue 1
- Ability for a canned query to write to the database · 5 ✖
id | html_url | issue_url | node_id | user | created_at ▼ | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
639779403 | https://github.com/simonw/datasette/issues/698#issuecomment-639779403 | https://api.github.com/repos/simonw/datasette/issues/698 | MDEyOklzc3VlQ29tbWVudDYzOTc3OTQwMw== | simonw 9599 | 2020-06-05T20:20:12Z | 2020-06-05T20:20:12Z | OWNER | CSRF is done. Last step: figure out a smart way to integrate this with permissions and authentication. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability for a canned query to write to the database 582517965 | |
639784651 | https://github.com/simonw/datasette/issues/698#issuecomment-639784651 | https://api.github.com/repos/simonw/datasette/issues/698 | MDEyOklzc3VlQ29tbWVudDYzOTc4NDY1MQ== | simonw 9599 | 2020-06-05T20:25:02Z | 2020-06-05T20:25:02Z | OWNER | Idea: default is anyone can execute a query. Or you can specify the following: ```json {
"databases": {
"my-database": {
"queries": {
"add_twitter_handle": {
"sql": "insert into twitter_handles (username) values (:username)",
"write": true,
"allow": {
"id": ["simon"],
"role": ["staff"]
}
}
}
}
}
}
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability for a canned query to write to the database 582517965 | |
639785878 | https://github.com/simonw/datasette/issues/698#issuecomment-639785878 | https://api.github.com/repos/simonw/datasette/issues/698 | MDEyOklzc3VlQ29tbWVudDYzOTc4NTg3OA== | simonw 9599 | 2020-06-05T20:25:55Z | 2020-06-05T20:25:55Z | OWNER | I'd really like to support SQL query defined permissions too, mainly to set an example for how plugins could do something similar. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability for a canned query to write to the database 582517965 | |
639787304 | https://github.com/simonw/datasette/issues/698#issuecomment-639787304 | https://api.github.com/repos/simonw/datasette/issues/698 | MDEyOklzc3VlQ29tbWVudDYzOTc4NzMwNA== | simonw 9599 | 2020-06-05T20:26:57Z | 2020-06-05T20:26:57Z | OWNER | Idea: an |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability for a canned query to write to the database 582517965 | |
639788562 | https://github.com/simonw/datasette/issues/698#issuecomment-639788562 | https://api.github.com/repos/simonw/datasette/issues/698 | MDEyOklzc3VlQ29tbWVudDYzOTc4ODU2Mg== | simonw 9599 | 2020-06-05T20:27:49Z | 2020-06-05T20:27:49Z | OWNER | There can be a detailed section explaining these different mechanisms on the authentication documentation page. I imagine they will end up applying to more than just canned queries. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability for a canned query to write to the database 582517965 |
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, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 1