issue_comments
22 rows where author_association = "OWNER", reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" and "updated_at" is on date 2023-08-23 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw 22
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1690787394 | https://github.com/simonw/datasette/issues/2143#issuecomment-1690787394 | https://api.github.com/repos/simonw/datasette/issues/2143 | IC_kwDOBm6k_c5kx15C | simonw 9599 | 2023-08-23T23:52:02Z | 2023-08-23T23:52:02Z | OWNER |
Having multiple configs that combine in that way is a really interesting direction.
I'm very keen on separating out the "metadata" - where metadata is the slimmest possible set of things, effectively the data license and the source and the column and table descriptions - from everything else, mainly because I want metadata to be able to travel with the data. One idea that's been discussed before is having an optional mechanism for storing metadata in the SQLite database file itself - potentially in a That's why I'm so keen on splitting out metadata from all of the other stuff - settings and plugin configuration and authentication rules. So really it becomes "true metadata" v.s. "all of the other junk that's accumulated in metadata and |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
De-tangling Metadata before Datasette 1.0 1855885427 | |
1690705243 | https://github.com/simonw/datasette/issues/2102#issuecomment-1690705243 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5kxh1b | simonw 9599 | 2023-08-23T22:03:54Z | 2023-08-23T22:03:54Z | OWNER | Idea: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1690703764 | https://github.com/simonw/datasette/issues/2102#issuecomment-1690703764 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5kxheU | simonw 9599 | 2023-08-23T22:02:14Z | 2023-08-23T22:02:14Z | OWNER | Built this new test:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1690693830 | https://github.com/simonw/datasette/issues/2102#issuecomment-1690693830 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5kxfDG | simonw 9599 | 2023-08-23T21:51:52Z | 2023-08-23T21:52:58Z | OWNER | This is the hook in question: https://github.com/simonw/datasette/blob/bdf59eb7db42559e538a637bacfe86d39e5d17ca/datasette/hookspecs.py#L108-L110
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
680262437 | https://github.com/simonw/datasette/issues/950#issuecomment-680262437 | https://api.github.com/repos/simonw/datasette/issues/950 | MDEyOklzc3VlQ29tbWVudDY4MDI2MjQzNw== | simonw 9599 | 2020-08-25T20:49:24Z | 2023-08-23T21:34:09Z | OWNER | The alternative to this would be to use regular databases and control access to them using Authentication and permissions. My concern there is that it's just too easy for someone to mess up their configuration, which would be really bad. I like the idea of a much stronger defense mechanism specifically designed for secrets that should not be exposed. Outside of secrets, passwords and tokens this mechanism could also be useful for the use-case of using Datasette to power websites - as seen on https://www.niche-museums.com/ and https://www.rockybeaches.com/ - maybe those sites don't want to expose their data through their API but still want to use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Private/secret databases: database files that are only visible to plugins 685806511 | |
1690438270 | https://github.com/simonw/datasette/issues/2150#issuecomment-1690438270 | https://api.github.com/repos/simonw/datasette/issues/2150 | IC_kwDOBm6k_c5kwgp- | simonw 9599 | 2023-08-23T18:27:47Z | 2023-08-23T18:27:47Z | OWNER | I added Oh interesting, looks like it's over-ridden here too: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
form label { width: 15% } is a bad default 1863810783 | |
1690435866 | https://github.com/simonw/datasette/issues/2150#issuecomment-1690435866 | https://api.github.com/repos/simonw/datasette/issues/2150 | IC_kwDOBm6k_c5kwgEa | simonw 9599 | 2023-08-23T18:25:51Z | 2023-08-23T18:25:51Z | OWNER | Looks like that affects a few forms: The search form on the table page over-rides it already: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
form label { width: 15% } is a bad default 1863810783 | |
1690432928 | https://github.com/simonw/datasette/issues/2150#issuecomment-1690432928 | https://api.github.com/repos/simonw/datasette/issues/2150 | IC_kwDOBm6k_c5kwfWg | simonw 9599 | 2023-08-23T18:23:26Z | 2023-08-23T18:23:26Z | OWNER | That should be scoped just to the query filters form on the table page. I'll fix it in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
form label { width: 15% } is a bad default 1863810783 | |
1690431509 | https://github.com/simonw/datasette/issues/2150#issuecomment-1690431509 | https://api.github.com/repos/simonw/datasette/issues/2150 | IC_kwDOBm6k_c5kwfAV | simonw 9599 | 2023-08-23T18:22:47Z | 2023-08-23T18:22:47Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
form label { width: 15% } is a bad default 1863810783 | ||
1690423878 | https://github.com/simonw/datasette/issues/2091#issuecomment-1690423878 | https://api.github.com/repos/simonw/datasette/issues/2091 | IC_kwDOBm6k_c5kwdJG | simonw 9599 | 2023-08-23T18:18:18Z | 2023-08-23T18:18:18Z | OWNER | Dupe of: - #2097 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Drop support for Python 3.7 1781022369 | |
1689206768 | https://github.com/simonw/datasette/issues/2147#issuecomment-1689206768 | https://api.github.com/repos/simonw/datasette/issues/2147 | IC_kwDOBm6k_c5krz_w | simonw 9599 | 2023-08-23T03:06:32Z | 2023-08-23T03:06:32Z | OWNER | I'm less convinced by the "rewrite the query in some way" optional idea. What kind of use-cases can you imagine for that? My hunch is that it's much more likely to cause weird breakages than it is to allow for useful plugin extensions, but I'm willing to be convinced otherwise. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for database queries that are run 1858228057 | |
1689206170 | https://github.com/simonw/datasette/issues/2147#issuecomment-1689206170 | https://api.github.com/repos/simonw/datasette/issues/2147 | IC_kwDOBm6k_c5krz2a | simonw 9599 | 2023-08-23T03:05:32Z | 2023-08-23T03:05:32Z | OWNER | Interestingly enough there's actually a mechanism that looks like that a bit already: https://github.com/simonw/datasette/blob/64fd1d788eeed2624f107ac699f2370590ae1aa3/datasette/views/database.py#L496-L508 That Against these constants: https://github.com/simonw/datasette/blob/64fd1d788eeed2624f107ac699f2370590ae1aa3/datasette/utils/init.py#L223-L253 Which isn't a million miles away from your suggestion to have a hook that can say if the query should be executed or not. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for database queries that are run 1858228057 | |
1689177556 | https://github.com/simonw/datasette/pull/2148#issuecomment-1689177556 | https://api.github.com/repos/simonw/datasette/issues/2148 | IC_kwDOBm6k_c5krs3U | simonw 9599 | 2023-08-23T02:44:29Z | 2023-08-23T02:44:29Z | OWNER | Simplest possible solution is to only run the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bump sphinx, furo, blacken-docs dependencies 1859415334 | |
1689175062 | https://github.com/simonw/datasette/pull/2148#issuecomment-1689175062 | https://api.github.com/repos/simonw/datasette/issues/2148 | IC_kwDOBm6k_c5krsQW | simonw 9599 | 2023-08-23T02:40:46Z | 2023-08-23T02:40:46Z | OWNER | Here's why the tests are failing: It looks like those tests don't actually need Sphinx installed - they install https://github.com/simonw/datasette/blob/2ce7872e3ba8d07248c194ef554bbdc1df510f32/setup.py#L70-L80 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bump sphinx, furo, blacken-docs dependencies 1859415334 | |
1689173748 | https://github.com/simonw/datasette/pull/2148#issuecomment-1689173748 | https://api.github.com/repos/simonw/datasette/issues/2148 | IC_kwDOBm6k_c5krr70 | simonw 9599 | 2023-08-23T02:38:31Z | 2023-08-23T02:38:31Z | OWNER | Sphinx dropped support for Python 3.8 in their version 7.2.0: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bump sphinx, furo, blacken-docs dependencies 1859415334 | |
1689159200 | https://github.com/simonw/datasette/issues/516#issuecomment-1689159200 | https://api.github.com/repos/simonw/datasette/issues/516 | IC_kwDOBm6k_c5kroYg | simonw 9599 | 2023-08-23T02:15:36Z | 2023-08-23T02:15:36Z | OWNER | This could play havoc with unmerged PRs. I should merge any big ones (like the JavaScript plugins work) first. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Enforce import sort order with isort 459509126 | |
1689158712 | https://github.com/simonw/datasette/issues/516#issuecomment-1689158712 | https://api.github.com/repos/simonw/datasette/issues/516 | IC_kwDOBm6k_c5kroQ4 | simonw 9599 | 2023-08-23T02:14:45Z | 2023-08-23T02:14:45Z | OWNER | Thinking about this again today. Posted about it on Discord: https://discord.com/channels/823971286308356157/823971286941302908/1143729300349132933 I won't enforce it in a https://github.com/simonw/datasette/blob/17ec309e14f9c2e90035ba33f2f38ecc5afba2fa/Justfile#L19-L23 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Enforce import sort order with isort 459509126 | |
1689154837 | https://github.com/simonw/datasette/issues/516#issuecomment-1689154837 | https://api.github.com/repos/simonw/datasette/issues/516 | IC_kwDOBm6k_c5krnUV | simonw 9599 | 2023-08-23T02:08:33Z | 2023-08-23T02:08:50Z | OWNER | Browse this commit to see the result: https://github.com/simonw/datasette/tree/59a5d336bd4336bc53103922ada4bf726f4336c9 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Enforce import sort order with isort 459509126 | |
1689153446 | https://github.com/simonw/datasette/issues/516#issuecomment-1689153446 | https://api.github.com/repos/simonw/datasette/issues/516 | IC_kwDOBm6k_c5krm-m | simonw 9599 | 2023-08-23T02:06:35Z | 2023-08-23T02:06:35Z | OWNER | I just tried this again today by dropping this into |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Enforce import sort order with isort 459509126 | |
1689130061 | https://github.com/simonw/datasette/pull/524#issuecomment-1689130061 | https://api.github.com/repos/simonw/datasette/issues/524 | IC_kwDOBm6k_c5krhRN | simonw 9599 | 2023-08-23T01:31:08Z | 2023-08-23T01:31:08Z | OWNER | This branch is WAY out of date. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Sort commits using isort, refs #516 459689615 | |
1689128553 | https://github.com/simonw/datasette/issues/275#issuecomment-1689128553 | https://api.github.com/repos/simonw/datasette/issues/275 | IC_kwDOBm6k_c5krg5p | simonw 9599 | 2023-08-23T01:28:37Z | 2023-08-23T01:28:37Z | OWNER | This is obsoleted by the work happening here: - #2093 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"config" section in metadata.json (root, database and table level) 324720095 | |
1689125244 | https://github.com/simonw/datasette/pull/2149#issuecomment-1689125244 | https://api.github.com/repos/simonw/datasette/issues/2149 | IC_kwDOBm6k_c5krgF8 | simonw 9599 | 2023-08-23T01:23:27Z | 2023-08-23T01:23:27Z | OWNER | This is a really great start - tests pass, implementation looks clean, the new stubbed documentation page makes sense. Let's land it in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Start a new `datasette.yaml` configuration file, with settings support 1861812208 |
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]);
issue 11