issue_comments
8,883 rows where user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
user 1
- simonw · 4,046 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
735484186 | https://github.com/dogsheep/github-to-sqlite/issues/51#issuecomment-735484186 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/51 | MDEyOklzc3VlQ29tbWVudDczNTQ4NDE4Ng== | simonw 9599 | 2020-11-30T00:29:31Z | 2020-11-30T00:29:31Z | MEMBER | This just caused a failure in deploying the demo: https://github.com/dogsheep/github-to-sqlite/runs/1471304407?check_suite_focus=true
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
github-to-sqlite should handle rate limits better 703246031 | |
735483820 | https://github.com/dogsheep/github-to-sqlite/issues/46#issuecomment-735483820 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/46 | MDEyOklzc3VlQ29tbWVudDczNTQ4MzgyMA== | simonw 9599 | 2020-11-30T00:27:47Z | 2020-11-30T00:27:47Z | MEMBER | So it looks like anything that pulls reviews needs to pull each review, then for each one pull the comments. I'm going to consider this blocked on smarter rate limit handling in #51. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Feature: pull request reviews and comments 664485022 | |
735483604 | https://github.com/dogsheep/github-to-sqlite/issues/46#issuecomment-735483604 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/46 | MDEyOklzc3VlQ29tbWVudDczNTQ4MzYwNA== | simonw 9599 | 2020-11-30T00:26:50Z | 2020-11-30T00:26:50Z | MEMBER | It seems like there's a lot missing from that - those aren't particularly interesting given the data that is returned. From the docs at https://docs.github.com/en/free-pro-team@latest/rest/reference/pulls#reviews it looks like each review consists of multiple comments, and the comments are where the useful material is - https://docs.github.com/en/free-pro-team@latest/rest/reference/pulls#list-comments-for-a-pull-request-review
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Feature: pull request reviews and comments 664485022 | |
735482546 | https://github.com/dogsheep/github-to-sqlite/issues/46#issuecomment-735482546 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/46 | MDEyOklzc3VlQ29tbWVudDczNTQ4MjU0Ng== | simonw 9599 | 2020-11-30T00:22:02Z | 2020-11-30T00:22:02Z | MEMBER | As for reviews... here's the output of
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Feature: pull request reviews and comments 664485022 | |
735482187 | https://github.com/dogsheep/github-to-sqlite/issues/46#issuecomment-735482187 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/46 | MDEyOklzc3VlQ29tbWVudDczNTQ4MjE4Nw== | simonw 9599 | 2020-11-30T00:20:11Z | 2020-11-30T00:20:11Z | MEMBER | Pull request are now added, thanks to @adamjonas. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Feature: pull request reviews and comments 664485022 | |
735465708 | https://github.com/dogsheep/github-to-sqlite/issues/54#issuecomment-735465708 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/54 | MDEyOklzc3VlQ29tbWVudDczNTQ2NTcwOA== | simonw 9599 | 2020-11-29T22:08:46Z | 2020-11-29T22:08:46Z | MEMBER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
github-to-sqlite workflows command 753026003 | ||
735464493 | https://github.com/dogsheep/github-to-sqlite/issues/54#issuecomment-735464493 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/54 | MDEyOklzc3VlQ29tbWVudDczNTQ2NDQ5Mw== | simonw 9599 | 2020-11-29T21:57:32Z | 2020-11-29T21:57:32Z | MEMBER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
github-to-sqlite workflows command 753026003 | |
735464438 | https://github.com/dogsheep/github-to-sqlite/issues/54#issuecomment-735464438 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/54 | MDEyOklzc3VlQ29tbWVudDczNTQ2NDQzOA== | simonw 9599 | 2020-11-29T21:57:08Z | 2020-11-29T21:57:08Z | MEMBER | Inspired by this tweet from Michael Heap https://twitter.com/mheap/status/1333108608817631238 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
github-to-sqlite workflows command 753026003 | |
735447635 | https://github.com/simonw/datasette/issues/1114#issuecomment-735447635 | https://api.github.com/repos/simonw/datasette/issues/1114 | MDEyOklzc3VlQ29tbWVudDczNTQ0NzYzNQ== | simonw 9599 | 2020-11-29T20:16:32Z | 2020-11-29T20:17:11Z | OWNER | The new Docker container is pushed to Docker Hub too. Here's it in action:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--load-extension=spatialite not working with datasetteproject/datasette docker image 752966476 | |
735447198 | https://github.com/simonw/datasette/issues/1115#issuecomment-735447198 | https://api.github.com/repos/simonw/datasette/issues/1115 | MDEyOklzc3VlQ29tbWVudDczNTQ0NzE5OA== | simonw 9599 | 2020-11-29T20:12:49Z | 2020-11-29T20:12:49Z | OWNER | ``` $ datasette ../shapefile-to-sqlite/nps-spatialite.db Usage: datasette serve [OPTIONS] [FILES]... Error: It looks like you're trying to load a SpatiaLite database without first loading the SpatiaLite module. Try adding the --load-extension=spatialite option. Read more: https://docs.datasette.io/en/stable/spatialite.html ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
SpatiaLite error could suggest --load-extension=spatialite 752995227 | |
735444858 | https://github.com/simonw/datasette/issues/1099#issuecomment-735444858 | https://api.github.com/repos/simonw/datasette/issues/1099 | MDEyOklzc3VlQ29tbWVudDczNTQ0NDg1OA== | simonw 9599 | 2020-11-29T19:51:58Z | 2020-11-29T19:51:58Z | OWNER | My fix in deb0be4ae56f191f121239b29e83dd53b62d6305 for #1098 was to have Datasette deliberately pretend that compound foreign keys don't exist: https://github.com/simonw/datasette/blob/deb0be4ae56f191f121239b29e83dd53b62d6305/datasette/utils/init.py#L470-L495 This workaround will need to be rethought to implement real support for them. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support linking to compound foreign keys 743371103 | |
735444698 | https://github.com/simonw/datasette/issues/1098#issuecomment-735444698 | https://api.github.com/repos/simonw/datasette/issues/1098 | MDEyOklzc3VlQ29tbWVudDczNTQ0NDY5OA== | simonw 9599 | 2020-11-29T19:50:14Z | 2020-11-29T19:50:14Z | OWNER | Demo of the fix: https://latest.datasette.io/fixtures/foreign_key_references (the compound foreign key columns do not link to anything) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign key links break for compound foreign keys 743370900 | |
735443654 | https://github.com/simonw/datasette/issues/1098#issuecomment-735443654 | https://api.github.com/repos/simonw/datasette/issues/1098 | MDEyOklzc3VlQ29tbWVudDczNTQ0MzY1NA== | simonw 9599 | 2020-11-29T19:41:01Z | 2020-11-29T19:41:01Z | OWNER | Fix is out in 0.52.1: https://docs.datasette.io/en/latest/changelog.html#v0-52-1 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign key links break for compound foreign keys 743370900 | |
735443626 | https://github.com/simonw/datasette/issues/1114#issuecomment-735443626 | https://api.github.com/repos/simonw/datasette/issues/1114 | MDEyOklzc3VlQ29tbWVudDczNTQ0MzYyNg== | simonw 9599 | 2020-11-29T19:40:49Z | 2020-11-29T19:40:49Z | OWNER | Fix is out in 0.52.1: https://docs.datasette.io/en/latest/changelog.html#v0-52-1 |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--load-extension=spatialite not working with datasetteproject/datasette docker image 752966476 | |
735442226 | https://github.com/simonw/datasette/issues/1098#issuecomment-735442226 | https://api.github.com/repos/simonw/datasette/issues/1098 | MDEyOklzc3VlQ29tbWVudDczNTQ0MjIyNg== | simonw 9599 | 2020-11-29T19:28:04Z | 2020-11-29T19:28:04Z | OWNER | For the moment I'm going to solve this by teaching Datasette's internal introspection methods - in particular these ones - to ignore compound foreign keys entirely: https://github.com/simonw/datasette/blob/e800ffcf7cc6a915eb554b369c654f87162575e5/datasette/utils/init.py#L470-L505 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign key links break for compound foreign keys 743370900 | |
735429041 | https://github.com/simonw/datasette/issues/1114#issuecomment-735429041 | https://api.github.com/repos/simonw/datasette/issues/1114 | MDEyOklzc3VlQ29tbWVudDczNTQyOTA0MQ== | simonw 9599 | 2020-11-29T17:36:18Z | 2020-11-29T17:36:18Z | OWNER | This is a great catch, thanks. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--load-extension=spatialite not working with datasetteproject/datasette docker image 752966476 | |
735356882 | https://github.com/simonw/datasette/issues/1102#issuecomment-735356882 | https://api.github.com/repos/simonw/datasette/issues/1102 | MDEyOklzc3VlQ29tbWVudDczNTM1Njg4Mg== | simonw 9599 | 2020-11-29T07:47:22Z | 2020-11-29T07:47:22Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin testing docs should show datasette.client 749289611 | ||
735320736 | https://github.com/simonw/datasette/issues/1111#issuecomment-735320736 | https://api.github.com/repos/simonw/datasette/issues/1111 | MDEyOklzc3VlQ29tbWVudDczNTMyMDczNg== | simonw 9599 | 2020-11-29T02:46:23Z | 2020-11-29T02:46:23Z | OWNER | This is a really useful bug report, thanks! I agree: more aggressive timeouts on table counts sounds like the right solution here. I've learned that avoiding |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Accessing a database's `.json` is slow for very large SQLite files 751195017 | |
735320499 | https://github.com/simonw/datasette/issues/1108#issuecomment-735320499 | https://api.github.com/repos/simonw/datasette/issues/1108 | MDEyOklzc3VlQ29tbWVudDczNTMyMDQ5OQ== | simonw 9599 | 2020-11-29T02:42:42Z | 2020-11-29T02:42:42Z | OWNER | https://docs.datasette.io/en/stable/config.html now redirects correctly. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Configure /en/stable/config.html redirect when I ship 0.52 750087350 | |
735304071 | https://github.com/simonw/datasette/issues/1113#issuecomment-735304071 | https://api.github.com/repos/simonw/datasette/issues/1113 | MDEyOklzc3VlQ29tbWVudDczNTMwNDA3MQ== | simonw 9599 | 2020-11-28T23:23:31Z | 2020-11-28T23:23:31Z | OWNER | https://github.com/simonw/datasette/blob/bbde835a1fec01458e8d00929e7bab6d6a5ba948/datasette/views/table.py#L1013-L1026 - looks like I fixed this in #1088. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
500 error on row page if query against foreign keys hits time limit 752789159 | |
735283033 | https://github.com/simonw/datasette/pull/1112#issuecomment-735283033 | https://api.github.com/repos/simonw/datasette/issues/1112 | MDEyOklzc3VlQ29tbWVudDczNTI4MzAzMw== | simonw 9599 | 2020-11-28T19:53:36Z | 2020-11-28T19:53:36Z | OWNER | Thanks! |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix --metadata doc usage 752749485 | |
733432916 | https://github.com/simonw/datasette/issues/1110#issuecomment-733432916 | https://api.github.com/repos/simonw/datasette/issues/1110 | MDEyOklzc3VlQ29tbWVudDczMzQzMjkxNg== | simonw 9599 | 2020-11-25T03:04:29Z | 2020-11-25T03:04:29Z | OWNER | Already have a pattern for extra packages in the form of the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette publish option for installing extra apt-get packages 750330029 | |
733432768 | https://github.com/simonw/datasette/issues/1110#issuecomment-733432768 | https://api.github.com/repos/simonw/datasette/issues/1110 | MDEyOklzc3VlQ29tbWVudDczMzQzMjc2OA== | simonw 9599 | 2020-11-25T03:04:00Z | 2020-11-25T03:04:00Z | OWNER | Design:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette publish option for installing extra apt-get packages 750330029 | |
733288841 | https://github.com/simonw/datasette/issues/860#issuecomment-733288841 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4ODg0MQ== | simonw 9599 | 2020-11-24T23:19:47Z | 2020-11-24T23:20:24Z | OWNER | Here's what I have today - it's an undocumented |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
733288522 | https://github.com/simonw/datasette/issues/860#issuecomment-733288522 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4ODUyMg== | simonw 9599 | 2020-11-24T23:18:47Z | 2020-11-24T23:18:47Z | OWNER | In #942 I want to add support for per-column metadata - which means this new lookup mechanism will need to be able to answer the question "what description is available for this column". So what should the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
733287619 | https://github.com/simonw/datasette/issues/860#issuecomment-733287619 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4NzYxOQ== | simonw 9599 | 2020-11-24T23:16:21Z | 2020-11-24T23:16:21Z | OWNER | I'll also allow any key to be looked up - so if users want to invent their own metadata keys other than the default |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
733287416 | https://github.com/simonw/datasette/issues/860#issuecomment-733287416 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4NzQxNg== | simonw 9599 | 2020-11-24T23:15:44Z | 2020-11-24T23:15:44Z | OWNER | I'm going to go with a plugin hook (and Datasette method) that returns individual values - so you ask it for e.g. the The default plugin hook implementation that ships with Datasette will then implement cascading lookups against |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
733261501 | https://github.com/simonw/datasette/issues/1107#issuecomment-733261501 | https://api.github.com/repos/simonw/datasette/issues/1107 | MDEyOklzc3VlQ29tbWVudDczMzI2MTUwMQ== | simonw 9599 | 2020-11-24T22:09:11Z | 2020-11-24T22:09:11Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename datasette.config() method to datasette.setting() 750079085 | ||
733257071 | https://github.com/simonw/datasette/issues/1107#issuecomment-733257071 | https://api.github.com/repos/simonw/datasette/issues/1107 | MDEyOklzc3VlQ29tbWVudDczMzI1NzA3MQ== | simonw 9599 | 2020-11-24T21:59:32Z | 2020-11-24T21:59:32Z | OWNER | I'm going to make this a documented method in https://docs.datasette.io/en/latest/internals.html#datasette-class |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename datasette.config() method to datasette.setting() 750079085 | |
733249176 | https://github.com/simonw/datasette/issues/1105#issuecomment-733249176 | https://api.github.com/repos/simonw/datasette/issues/1105 | MDEyOklzc3VlQ29tbWVudDczMzI0OTE3Ng== | simonw 9599 | 2020-11-24T21:40:28Z | 2020-11-24T21:40:28Z | OWNER | This rebranding is complete - #1107 is a follow-up internal refactor. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rebrand config as settings 749982022 | |
733248437 | https://github.com/simonw/datasette/issues/1106#issuecomment-733248437 | https://api.github.com/repos/simonw/datasette/issues/1106 | MDEyOklzc3VlQ29tbWVudDczMzI0ODQzNw== | simonw 9599 | 2020-11-24T21:38:50Z | 2020-11-24T21:38:50Z | OWNER | I used an "exact redirect" instead and it worked: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rebrand and redirect config.rst as settings.rst 749983857 | |
733247101 | https://github.com/simonw/datasette/issues/1106#issuecomment-733247101 | https://api.github.com/repos/simonw/datasette/issues/1106 | MDEyOklzc3VlQ29tbWVudDczMzI0NzEwMQ== | simonw 9599 | 2020-11-24T21:35:29Z | 2020-11-24T21:36:04Z | OWNER | https://docs.datasette.io/en/latest/config.html isn't redirecting though, even after I tried running a rebuild of the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rebrand and redirect config.rst as settings.rst 749983857 | |
733245596 | https://github.com/simonw/datasette/issues/1106#issuecomment-733245596 | https://api.github.com/repos/simonw/datasette/issues/1106 | MDEyOklzc3VlQ29tbWVudDczMzI0NTU5Ng== | simonw 9599 | 2020-11-24T21:32:11Z | 2020-11-24T21:32:11Z | OWNER | https://docs.datasette.io/en/latest/settings.html is now live - need to redirect https://docs.datasette.io/en/latest/config.html to it using the ReadTheDocs redirects interface. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rebrand and redirect config.rst as settings.rst 749983857 | |
733245097 | https://github.com/simonw/datasette/issues/1107#issuecomment-733245097 | https://api.github.com/repos/simonw/datasette/issues/1107 | MDEyOklzc3VlQ29tbWVudDczMzI0NTA5Nw== | simonw 9599 | 2020-11-24T21:31:10Z | 2020-11-24T21:31:10Z | OWNER | Most of these use
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename datasette.config() method to datasette.setting() 750079085 | |
733244471 | https://github.com/simonw/datasette/issues/1107#issuecomment-733244471 | https://api.github.com/repos/simonw/datasette/issues/1107 | MDEyOklzc3VlQ29tbWVudDczMzI0NDQ3MQ== | simonw 9599 | 2020-11-24T21:29:59Z | 2020-11-24T21:29:59Z | OWNER | I ran |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename datasette.config() method to datasette.setting() 750079085 | |
733241949 | https://github.com/simonw/datasette/issues/1107#issuecomment-733241949 | https://api.github.com/repos/simonw/datasette/issues/1107 | MDEyOklzc3VlQ29tbWVudDczMzI0MTk0OQ== | simonw 9599 | 2020-11-24T21:24:26Z | 2020-11-24T21:24:26Z | OWNER | Are there any plugins that use this API even though it isn't documented? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename datasette.config() method to datasette.setting() 750079085 | |
733221359 | https://github.com/simonw/datasette/issues/1106#issuecomment-733221359 | https://api.github.com/repos/simonw/datasette/issues/1106 | MDEyOklzc3VlQ29tbWVudDczMzIyMTM1OQ== | simonw 9599 | 2020-11-24T20:40:21Z | 2020-11-24T20:40:21Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rebrand and redirect config.rst as settings.rst 749983857 | ||
733212084 | https://github.com/simonw/datasette/issues/1104#issuecomment-733212084 | https://api.github.com/repos/simonw/datasette/issues/1104 | MDEyOklzc3VlQ29tbWVudDczMzIxMjA4NA== | simonw 9599 | 2020-11-24T20:20:33Z | 2020-11-24T20:20:33Z | OWNER | I'll throw an error if a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
config.json in directory config mode should be settings.json 749981663 | |
733198051 | https://github.com/simonw/datasette/issues/226#issuecomment-733198051 | https://api.github.com/repos/simonw/datasette/issues/226 | MDEyOklzc3VlQ29tbWVudDczMzE5ODA1MQ== | simonw 9599 | 2020-11-24T19:52:46Z | 2020-11-24T19:52:46Z | OWNER | This is well handled now: https://github.com/simonw/datasette/tree/0.51.1/tests/plugins |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unit tests for installable plugins 315738696 | |
733190827 | https://github.com/simonw/datasette/issues/1105#issuecomment-733190827 | https://api.github.com/repos/simonw/datasette/issues/1105 | MDEyOklzc3VlQ29tbWVudDczMzE5MDgyNw== | simonw 9599 | 2020-11-24T19:38:02Z | 2020-11-24T19:38:02Z | OWNER | I'd like to redirect https://docs.datasette.io/en/stable/config.html to a new https://docs.datasette.io/en/stable/settings.html page too. I can use https://docs.readthedocs.io/en/stable/user-defined-redirects.html for that. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rebrand config as settings 749982022 | |
733189737 | https://github.com/simonw/datasette/issues/1103#issuecomment-733189737 | https://api.github.com/repos/simonw/datasette/issues/1103 | MDEyOklzc3VlQ29tbWVudDczMzE4OTczNw== | simonw 9599 | 2020-11-24T19:35:45Z | 2020-11-24T19:35:45Z | OWNER | Part of #1105 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename /-/config to /-/settings 749979454 | |
733189693 | https://github.com/simonw/datasette/issues/992#issuecomment-733189693 | https://api.github.com/repos/simonw/datasette/issues/992 | MDEyOklzc3VlQ29tbWVudDczMzE4OTY5Mw== | simonw 9599 | 2020-11-24T19:35:38Z | 2020-11-24T19:35:38Z | OWNER | Part of #1105 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Change "--config foo:bar" to "--setting foo bar" 714449879 | |
733189620 | https://github.com/simonw/datasette/issues/1104#issuecomment-733189620 | https://api.github.com/repos/simonw/datasette/issues/1104 | MDEyOklzc3VlQ29tbWVudDczMzE4OTYyMA== | simonw 9599 | 2020-11-24T19:35:30Z | 2020-11-24T19:35:30Z | OWNER | Part of #1105 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
config.json in directory config mode should be settings.json 749981663 | |
733187586 | https://github.com/simonw/datasette/issues/1103#issuecomment-733187586 | https://api.github.com/repos/simonw/datasette/issues/1103 | MDEyOklzc3VlQ29tbWVudDczMzE4NzU4Ng== | simonw 9599 | 2020-11-24T19:31:23Z | 2020-11-24T19:31:23Z | OWNER | I'll set up a redirect from |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename /-/config to /-/settings 749979454 | |
733180289 | https://github.com/simonw/datasette/issues/992#issuecomment-733180289 | https://api.github.com/repos/simonw/datasette/issues/992 | MDEyOklzc3VlQ29tbWVudDczMzE4MDI4OQ== | simonw 9599 | 2020-11-24T19:16:30Z | 2020-11-24T19:16:30Z | OWNER | Need to figure out the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Change "--config foo:bar" to "--setting foo bar" 714449879 | |
733176252 | https://github.com/simonw/datasette/issues/992#issuecomment-733176252 | https://api.github.com/repos/simonw/datasette/issues/992 | MDEyOklzc3VlQ29tbWVudDczMzE3NjI1Mg== | simonw 9599 | 2020-11-24T19:07:49Z | 2020-11-24T19:07:49Z | OWNER | I'm going to keep |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Change "--config foo:bar" to "--setting foo bar" 714449879 | |
733175965 | https://github.com/simonw/datasette/issues/992#issuecomment-733175965 | https://api.github.com/repos/simonw/datasette/issues/992 | MDEyOklzc3VlQ29tbWVudDczMzE3NTk2NQ== | simonw 9599 | 2020-11-24T19:07:13Z | 2020-11-24T19:07:13Z | OWNER | This is blocking progress on other metadata tickets like #860 because I want to split the concept of concrete metadata (source, license, etc) from configuration that currently lives in metadata (default sort order, default facets). I'm going to solve this next to unblock that stuff. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Change "--config foo:bar" to "--setting foo bar" 714449879 | |
733175454 | https://github.com/simonw/datasette/issues/860#issuecomment-733175454 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzE3NTQ1NA== | simonw 9599 | 2020-11-24T19:06:07Z | 2020-11-24T19:06:07Z | OWNER | I see two ways this plugin hook could work. It could be asked about a specific instance, database or table and return the full metadata for that object. OR it could ask for a specific metadata field - e.g. The more finely grained one would allow plugins to implement their own cascading rules pretty easily. Is there a reason it would be better for the hook to return an entire block of JSON for a specific table or database? I also need to decide if this hook is just going to be about source/license/about displayed metadata, or if it will include the functionality that has been sneaking into Perhaps I should split those out into a "configuration" concept first, after renaming |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
732544590 | https://github.com/simonw/datasette/issues/1101#issuecomment-732544590 | https://api.github.com/repos/simonw/datasette/issues/1101 | MDEyOklzc3VlQ29tbWVudDczMjU0NDU5MA== | simonw 9599 | 2020-11-24T02:22:55Z | 2020-11-24T02:22:55Z | OWNER | The trick I'm using here is to follow the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
register_output_renderer() should support streaming data 749283032 | |
732543700 | https://github.com/simonw/datasette/issues/1101#issuecomment-732543700 | https://api.github.com/repos/simonw/datasette/issues/1101 | MDEyOklzc3VlQ29tbWVudDczMjU0MzcwMA== | simonw 9599 | 2020-11-24T02:20:30Z | 2020-11-24T02:20:30Z | OWNER | Current design: https://docs.datasette.io/en/stable/plugin_hooks.html#register-output-renderer-datasette
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
register_output_renderer() should support streaming data 749283032 | |
732542285 | https://github.com/simonw/datasette/issues/1096#issuecomment-732542285 | https://api.github.com/repos/simonw/datasette/issues/1096 | MDEyOklzc3VlQ29tbWVudDczMjU0MjI4NQ== | simonw 9599 | 2020-11-24T02:16:22Z | 2020-11-24T02:16:22Z | OWNER | I'd like to implement this by first extending the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
TSV should be a default export option 743359646 | |
731658059 | https://github.com/simonw/datasette/issues/860#issuecomment-731658059 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMTY1ODA1OQ== | simonw 9599 | 2020-11-22T00:31:47Z | 2020-11-22T00:33:48Z | OWNER | Documented behaviour right now, for metadata set at the instance level, is: https://docs.datasette.io/en/stable/metadata.html
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
731657660 | https://github.com/simonw/datasette/issues/860#issuecomment-731657660 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMTY1NzY2MA== | simonw 9599 | 2020-11-22T00:27:32Z | 2020-11-22T00:31:54Z | OWNER | Open question: how should cascading work? If a table is missing a field but the database or instance has it, should that value cascade down to the table? It feels like But... should the other fields cascade? Cascading What about |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
731657486 | https://github.com/simonw/datasette/issues/860#issuecomment-731657486 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMTY1NzQ4Ng== | simonw 9599 | 2020-11-22T00:25:34Z | 2020-11-22T00:25:34Z | OWNER | There are three layers of metadata: table, database and instance. Currently the metadata fields are (ignoring not-quite-metadata like
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
731654132 | https://github.com/simonw/datasette/issues/1084#issuecomment-731654132 | https://api.github.com/repos/simonw/datasette/issues/1084 | MDEyOklzc3VlQ29tbWVudDczMTY1NDEzMg== | simonw 9599 | 2020-11-21T23:45:59Z | 2020-11-21T23:45:59Z | OWNER | https://datasette-graphql-demo.datasette.io/github/users now demonstrates the fix. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Table/database action menu cut off if too short 737394470 | |
731653083 | https://github.com/simonw/datasette/issues/1084#issuecomment-731653083 | https://api.github.com/repos/simonw/datasette/issues/1084 | MDEyOklzc3VlQ29tbWVudDczMTY1MzA4Mw== | simonw 9599 | 2020-11-21T23:35:07Z | 2020-11-21T23:35:07Z | OWNER | I got to use CSS |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Table/database action menu cut off if too short 737394470 | |
731652991 | https://github.com/simonw/datasette/issues/1084#issuecomment-731652991 | https://api.github.com/repos/simonw/datasette/issues/1084 | MDEyOklzc3VlQ29tbWVudDczMTY1Mjk5MQ== | simonw 9599 | 2020-11-21T23:34:22Z | 2020-11-21T23:34:22Z | OWNER | Fixed by positioning the menu relative to the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Table/database action menu cut off if too short 737394470 | |
731644064 | https://github.com/simonw/datasette/issues/1084#issuecomment-731644064 | https://api.github.com/repos/simonw/datasette/issues/1084 | MDEyOklzc3VlQ29tbWVudDczMTY0NDA2NA== | simonw 9599 | 2020-11-21T22:10:15Z | 2020-11-21T22:10:15Z | OWNER | Another example of this bug: https://datasette-graphql-demo.datasette.io/github/users |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Table/database action menu cut off if too short 737394470 | |
728262974 | https://github.com/simonw/datasette/issues/1091#issuecomment-728262974 | https://api.github.com/repos/simonw/datasette/issues/1091 | MDEyOklzc3VlQ29tbWVudDcyODI2Mjk3NA== | simonw 9599 | 2020-11-16T19:05:08Z | 2020-11-16T19:05:08Z | OWNER | I have a hunch that there may be some extra configuration in play here - could Apache itself be rewriting some of the links using mod_proxy_html? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.json and .csv exports fail to apply base_url 742011049 | |
727692413 | https://github.com/dogsheep/swarm-to-sqlite/issues/11#issuecomment-727692413 | https://api.github.com/repos/dogsheep/swarm-to-sqlite/issues/11 | MDEyOklzc3VlQ29tbWVudDcyNzY5MjQxMw== | simonw 9599 | 2020-11-16T02:15:22Z | 2020-11-16T02:15:22Z | MEMBER | Thanks, I'll look into this. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error thrown: sqlite3.OperationalError: table users has no column named lastName 743400216 | |
727656208 | https://github.com/simonw/datasette/issues/1098#issuecomment-727656208 | https://api.github.com/repos/simonw/datasette/issues/1098 | MDEyOklzc3VlQ29tbWVudDcyNzY1NjIwOA== | simonw 9599 | 2020-11-15T23:26:14Z | 2020-11-15T23:26:14Z | OWNER | Schema for that broken example:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign key links break for compound foreign keys 743370900 | |
727655636 | https://github.com/simonw/datasette/issues/1098#issuecomment-727655636 | https://api.github.com/repos/simonw/datasette/issues/1098 | MDEyOklzc3VlQ29tbWVudDcyNzY1NTYzNg== | simonw 9599 | 2020-11-15T23:22:27Z | 2020-11-15T23:22:27Z | OWNER | Need to replicate this in the fixtures, then fix it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign key links break for compound foreign keys 743370900 | |
727626657 | https://github.com/simonw/datasette/issues/942#issuecomment-727626657 | https://api.github.com/repos/simonw/datasette/issues/942 | MDEyOklzc3VlQ29tbWVudDcyNzYyNjY1Nw== | simonw 9599 | 2020-11-15T19:54:44Z | 2020-11-15T19:54:44Z | OWNER | This will also benefit from the metadata plugin hook: #860 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support column descriptions in metadata.json 681334912 | |
727233553 | https://github.com/simonw/datasette/issues/1091#issuecomment-727233553 | https://api.github.com/repos/simonw/datasette/issues/1091 | MDEyOklzc3VlQ29tbWVudDcyNzIzMzU1Mw== | simonw 9599 | 2020-11-14T16:46:52Z | 2020-11-14T16:46:52Z | OWNER | @tballison could I see the section of your Apache config that configures the proxying to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.json and .csv exports fail to apply base_url 742011049 | |
726419027 | https://github.com/simonw/datasette/issues/268#issuecomment-726419027 | https://api.github.com/repos/simonw/datasette/issues/268 | MDEyOklzc3VlQ29tbWVudDcyNjQxOTAyNw== | simonw 9599 | 2020-11-13T00:09:04Z | 2020-11-13T00:09:04Z | OWNER | Part of the challenge here is that this is the first time the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for ranking results from SQLite full-text search 323718842 | |
726417847 | https://github.com/simonw/datasette/issues/749#issuecomment-726417847 | https://api.github.com/repos/simonw/datasette/issues/749 | MDEyOklzc3VlQ29tbWVudDcyNjQxNzg0Nw== | simonw 9599 | 2020-11-13T00:05:14Z | 2020-11-13T00:05:14Z | OWNER | https://cloud.google.com/blog/products/serverless/cloud-run-now-supports-http-grpc-server-streaming indicates this limit should no longer apply:
But I'm still getting errors from Cloud Run attempting to download I filed a question in their issue tracker about that here: https://issuetracker.google.com/issues/173038375 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Cloud Run fails to serve database files larger than 32MB 610829227 | |
726416330 | https://github.com/simonw/datasette/issues/1091#issuecomment-726416330 | https://api.github.com/repos/simonw/datasette/issues/1091 | MDEyOklzc3VlQ29tbWVudDcyNjQxNjMzMA== | simonw 9599 | 2020-11-13T00:00:43Z | 2020-11-13T00:00:43Z | OWNER | Here's where |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.json and .csv exports fail to apply base_url 742011049 | |
726415991 | https://github.com/simonw/datasette/issues/1091#issuecomment-726415991 | https://api.github.com/repos/simonw/datasette/issues/1091 | MDEyOklzc3VlQ29tbWVudDcyNjQxNTk5MQ== | simonw 9599 | 2020-11-12T23:59:34Z | 2020-11-12T23:59:34Z | OWNER | The sort headers are generated by this template code: https://github.com/simonw/datasette/blob/5eb8e9bf250b26e30b017d39a392c33973997656/datasette/templates/_table.html#L11-L15 The export links use this code: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.json and .csv exports fail to apply base_url 742011049 | |
726415019 | https://github.com/simonw/datasette/issues/1091#issuecomment-726415019 | https://api.github.com/repos/simonw/datasette/issues/1091 | MDEyOklzc3VlQ29tbWVudDcyNjQxNTAxOQ== | simonw 9599 | 2020-11-12T23:56:23Z | 2020-11-12T23:56:23Z | OWNER | @tballison is there any chance you're running any custom templates in that installation? I'm really confused as to why I can't replicate the bug. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.json and .csv exports fail to apply base_url 742011049 | |
726413829 | https://github.com/simonw/datasette/issues/1091#issuecomment-726413829 | https://api.github.com/repos/simonw/datasette/issues/1091 | MDEyOklzc3VlQ29tbWVudDcyNjQxMzgyOQ== | simonw 9599 | 2020-11-12T23:52:50Z | 2020-11-12T23:54:16Z | OWNER | Hmm... it's not just the This data as json, CSV ( advanced)
<table class="rows-and-columns">
<thead>
<tr>
<th class="col-Link" scope="col" data-column="Link" data-column-type="" data-column-not-null="0" data-is-pk="0">
Link
</th>
<th class="col-rowid" scope="col" data-column="rowid" data-column-type="integer" data-column-not-null="0" data-is-pk="1">
rowid ▼
</th>
<th class="col-PARSE_EXCEPTION_ID" scope="col" data-column="PARSE_EXCEPTION_ID" data-column-type="INTEGER" data-column-not-null="0" data-is-pk="0">
PARSE_EXCEPTION_ID
</th>
<th class="col-PARSE_EXCEPTION_DESCRIPTION" scope="col" data-column="PARSE_EXCEPTION_DESCRIPTION" data-column-type="VARCHAR(128)" data-column-not-null="0" data-is-pk="0">
PARSE_EXCEPTION_DESCRIPTION
</th>
</tr>
</thead>
<tbody>
<tr>
<td class="col-Link type-pk">
1
</td>
<td class="col-rowid type-int">1</td>
<td class="col-PARSE_EXCEPTION_ID type-int">0</td>
<td class="col-PARSE_EXCEPTION_DESCRIPTION type-str">RUNTIME</td>
</tr>
<tr>
<td class="col-Link type-pk">
2
</td>
<td class="col-rowid type-int">2</td>
<td class="col-PARSE_EXCEPTION_ID type-int">1</td>
<td class="col-PARSE_EXCEPTION_DESCRIPTION type-str">ENCRYPTION</td>
</tr>
<tr>
<td class="col-Link type-pk">
3
</td>
<td class="col-rowid type-int">3</td>
<td class="col-PARSE_EXCEPTION_ID type-int">2</td>
<td class="col-PARSE_EXCEPTION_DESCRIPTION type-str">ACCESS_PERMISSION</td>
</tr>
<tr>
<td class="col-Link type-pk">
4
</td>
<td class="col-rowid type-int">4</td>
<td class="col-PARSE_EXCEPTION_ID type-int">3</td>
<td class="col-PARSE_EXCEPTION_DESCRIPTION type-str">UNSUPPORTED_VERSION</td>
</tr>
</tbody>
</table>
Advanced exportJSON shape: default, array, newline-delimited <form action="/corpora-metadata/REF_PARSE_EXCEPTION_TYPES.csv" method="get">CSV options: <label> download file </label> </form>
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.json and .csv exports fail to apply base_url 742011049 | |
726412057 | https://github.com/simonw/datasette/issues/865#issuecomment-726412057 | https://api.github.com/repos/simonw/datasette/issues/865 | MDEyOklzc3VlQ29tbWVudDcyNjQxMjA1Nw== | simonw 9599 | 2020-11-12T23:49:23Z | 2020-11-12T23:49:23Z | OWNER | @tballison thanks, I've split that out into a new issue #1091 |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
base_url doesn't seem to work when adding criteria and clicking "apply" 644582921 | |
726127465 | https://github.com/simonw/datasette/issues/1089#issuecomment-726127465 | https://api.github.com/repos/simonw/datasette/issues/1089 | MDEyOklzc3VlQ29tbWVudDcyNjEyNzQ2NQ== | simonw 9599 | 2020-11-12T14:54:11Z | 2020-11-12T14:54:11Z | OWNER | Suggested list to look out for from that PR:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Sweep documentation for words that minimize involved difficulty 741665726 | |
725830716 | https://github.com/simonw/datasette/issues/1088#issuecomment-725830716 | https://api.github.com/repos/simonw/datasette/issues/1088 | MDEyOklzc3VlQ29tbWVudDcyNTgzMDcxNg== | simonw 9599 | 2020-11-12T04:35:38Z | 2020-11-12T04:35:38Z | OWNER | I'm going to fix this without a test, because writing a test for this is a bit fiddly and it's a very minor bug. If it comes back again I'll do the work to test for it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
OperationalError('interrupted') can 500 on row page 741268956 | |
725830533 | https://github.com/simonw/datasette/issues/1088#issuecomment-725830533 | https://api.github.com/repos/simonw/datasette/issues/1088 | MDEyOklzc3VlQ29tbWVudDcyNTgzMDUzMw== | simonw 9599 | 2020-11-12T04:35:08Z | 2020-11-12T04:35:08Z | OWNER | Yup, swapping |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
OperationalError('interrupted') can 500 on row page 741268956 | |
725829903 | https://github.com/simonw/datasette/issues/1088#issuecomment-725829903 | https://api.github.com/repos/simonw/datasette/issues/1088 | MDEyOklzc3VlQ29tbWVudDcyNTgyOTkwMw== | simonw 9599 | 2020-11-12T04:33:14Z | 2020-11-12T04:33:14Z | OWNER | I'm suspicious of this code: https://github.com/simonw/datasette/blob/e8e0a6f284ca953b2980186c4356594c07bd1929/datasette/views/table.py#L1032-L1045 This code uses a different exception: https://github.com/simonw/datasette/blob/e8e0a6f284ca953b2980186c4356594c07bd1929/datasette/views/table.py#L658-L663 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
OperationalError('interrupted') can 500 on row page 741268956 | |
725729857 | https://github.com/simonw/datasette/issues/1086#issuecomment-725729857 | https://api.github.com/repos/simonw/datasette/issues/1086 | MDEyOklzc3VlQ29tbWVudDcyNTcyOTg1Nw== | simonw 9599 | 2020-11-11T23:55:39Z | 2020-11-11T23:55:39Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign keys with blank titles result in non-clickable links 741021342 | ||
725714908 | https://github.com/simonw/datasette/issues/1086#issuecomment-725714908 | https://api.github.com/repos/simonw/datasette/issues/1086 | MDEyOklzc3VlQ29tbWVudDcyNTcxNDkwOA== | simonw 9599 | 2020-11-11T23:17:26Z | 2020-11-11T23:17:26Z | OWNER | I'm just going to use a regular coloured hyphen. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign keys with blank titles result in non-clickable links 741021342 | |
725622784 | https://github.com/simonw/datasette/issues/1086#issuecomment-725622784 | https://api.github.com/repos/simonw/datasette/issues/1086 | MDEyOklzc3VlQ29tbWVudDcyNTYyMjc4NA== | simonw 9599 | 2020-11-11T19:41:45Z | 2020-11-11T19:41:45Z | OWNER | Maybe use a grey hyphen here? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Foreign keys with blank titles result in non-clickable links 741021342 | |
723829147 | https://github.com/simonw/sqlite-utils/issues/168#issuecomment-723829147 | https://api.github.com/repos/simonw/sqlite-utils/issues/168 | MDEyOklzc3VlQ29tbWVudDcyMzgyOTE0Nw== | simonw 9599 | 2020-11-09T07:43:30Z | 2020-11-09T07:43:30Z | OWNER | Yeah whatever process the have in place is working great without any extra intervention: they upgraded to 3.0 four hours ago. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automate (as much as possible) updates published to Homebrew 706167456 | |
723740546 | https://github.com/simonw/datasette/issues/268#issuecomment-723740546 | https://api.github.com/repos/simonw/datasette/issues/268 | MDEyOklzc3VlQ29tbWVudDcyMzc0MDU0Ng== | simonw 9599 | 2020-11-09T04:01:50Z | 2020-11-09T04:01:50Z | OWNER | I should depend on |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for ranking results from SQLite full-text search 323718842 | |
723637930 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-723637930 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMzYzNzkzMA== | simonw 9599 | 2020-11-08T17:06:56Z | 2020-11-08T17:06:56Z | OWNER | This looks pretty good now! ``` % sqlite-utils search 24ways.db articles simon -c title -c author -t title author Don't be eval() Simon Willison DOM Scripting Your Way to Better Blockquotes Jeremy Keith Swooshy Curly Quotes Without Images Simon Collison The Articulate Web Designer of Tomorrow Simon Collison Writing Responsible JavaScript Drew McLellan Going Nuts with CSS Transitions Natalie Downe Managing a Mind Christopher Murphy Design Systems Laura Kalbag Bringing Your Code to the Streets Ruth John Taming Complexity Simon Collison Unobtrusively Mapping Microformats with jQuery Simon Willison Crafting the Front-end Ben Bodien Develop Your Naturalist Superpowers with Observable Notebooks and iNaturalist Natalie Downe Fast Autocomplete Search for Your Website Simon Willison ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
723369033 | https://github.com/simonw/sqlite-utils/issues/201#issuecomment-723369033 | https://api.github.com/repos/simonw/sqlite-utils/issues/201 | MDEyOklzc3VlQ29tbWVudDcyMzM2OTAzMw== | simonw 9599 | 2020-11-07T01:28:11Z | 2020-11-07T01:28:11Z | OWNER | Need to fix this to close #192 and #197. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.search(columns=) and sqlite-utils search -c ... bug 738128913 | |
723368528 | https://github.com/simonw/sqlite-utils/issues/194#issuecomment-723368528 | https://api.github.com/repos/simonw/sqlite-utils/issues/194 | MDEyOklzc3VlQ29tbWVudDcyMzM2ODUyOA== | simonw 9599 | 2020-11-07T01:24:55Z | 2020-11-07T01:24:55Z | OWNER | Here's the alpha release: https://github.com/simonw/sqlite-utils/releases/tag/3.0a0 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
3.0 release with some minor breaking changes 735650864 | |
723365651 | https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723365651 | https://api.github.com/repos/simonw/sqlite-utils/issues/197 | MDEyOklzc3VlQ29tbWVudDcyMzM2NTY1MQ== | simonw 9599 | 2020-11-07T01:06:32Z | 2020-11-07T01:06:32Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rethink how table.search() method works 737153927 | ||
723360842 | https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723360842 | https://api.github.com/repos/simonw/sqlite-utils/issues/197 | MDEyOklzc3VlQ29tbWVudDcyMzM2MDg0Mg== | simonw 9599 | 2020-11-07T00:40:55Z | 2020-11-07T00:40:55Z | OWNER | The |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rethink how table.search() method works 737153927 | |
723357855 | https://github.com/simonw/sqlite-utils/issues/200#issuecomment-723357855 | https://api.github.com/repos/simonw/sqlite-utils/issues/200 | MDEyOklzc3VlQ29tbWVudDcyMzM1Nzg1NQ== | simonw 9599 | 2020-11-07T00:24:37Z | 2020-11-07T00:24:37Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils rows -c option 738115165 | |
723357117 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-723357117 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMzM1NzExNw== | simonw 9599 | 2020-11-07T00:21:05Z | 2020-11-07T00:21:05Z | OWNER | I'm going to have it only output the exact |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
723356020 | https://github.com/simonw/sqlite-utils/issues/194#issuecomment-723356020 | https://api.github.com/repos/simonw/sqlite-utils/issues/194 | MDEyOklzc3VlQ29tbWVudDcyMzM1NjAyMA== | simonw 9599 | 2020-11-07T00:16:06Z | 2020-11-07T00:16:06Z | OWNER | I'm going to release this as an alpha first and sit on it for a few days, since I don't want to ship any mistakes that would result in having to bump straight to 4.0! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
3.0 release with some minor breaking changes 735650864 | |
723350956 | https://github.com/simonw/sqlite-utils/issues/91#issuecomment-723350956 | https://api.github.com/repos/simonw/sqlite-utils/issues/91 | MDEyOklzc3VlQ29tbWVudDcyMzM1MDk1Ng== | simonw 9599 | 2020-11-06T23:53:25Z | 2020-11-06T23:53:25Z | OWNER | This is now possible, for both FTS4 and FTS5 - see #197. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Enable ordering FTS results by rank 577302229 | |
723348722 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-723348722 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMzM0ODcyMg== | simonw 9599 | 2020-11-06T23:43:09Z | 2020-11-06T23:43:09Z | OWNER | Also that order looks incorrect. It looks like most relevant came back last, not first. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
723348614 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-723348614 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMzM0ODYxNA== | simonw 9599 | 2020-11-06T23:42:38Z | 2020-11-06T23:42:38Z | OWNER | This is a bit surprising:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
723234493 | https://github.com/simonw/sqlite-utils/issues/194#issuecomment-723234493 | https://api.github.com/repos/simonw/sqlite-utils/issues/194 | MDEyOklzc3VlQ29tbWVudDcyMzIzNDQ5Mw== | simonw 9599 | 2020-11-06T18:32:34Z | 2020-11-06T18:32:34Z | OWNER | The breaking changes will be:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
3.0 release with some minor breaking changes 735650864 | |
723230732 | https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723230732 | https://api.github.com/repos/simonw/sqlite-utils/issues/197 | MDEyOklzc3VlQ29tbWVudDcyMzIzMDczMg== | simonw 9599 | 2020-11-06T18:24:29Z | 2020-11-06T18:24:29Z | OWNER | Still need to update docs. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rethink how table.search() method works 737153927 | |
723148906 | https://github.com/simonw/sqlite-utils/pull/195#issuecomment-723148906 | https://api.github.com/repos/simonw/sqlite-utils/issues/195 | MDEyOklzc3VlQ29tbWVudDcyMzE0ODkwNg== | simonw 9599 | 2020-11-06T15:43:51Z | 2020-11-06T15:43:51Z | OWNER | Thanks to #198 (introducing a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
table.search() improvements plus sqlite-utils search command 735663855 | |
723148310 | https://github.com/simonw/sqlite-utils/issues/197#issuecomment-723148310 | https://api.github.com/repos/simonw/sqlite-utils/issues/197 | MDEyOklzc3VlQ29tbWVudDcyMzE0ODMxMA== | simonw 9599 | 2020-11-06T15:42:43Z | 2020-11-06T15:42:43Z | OWNER | Having |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rethink how table.search() method works 737153927 | |
723147463 | https://github.com/simonw/sqlite-utils/issues/199#issuecomment-723147463 | https://api.github.com/repos/simonw/sqlite-utils/issues/199 | MDEyOklzc3VlQ29tbWVudDcyMzE0NzQ2Mw== | simonw 9599 | 2020-11-06T15:41:00Z | 2020-11-06T15:41:00Z | OWNER | Something like this:
It defaults to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
@db.register_function(..., replace=False) to avoid double-registering custom functions 737855731 | |
723145383 | https://github.com/simonw/sqlite-utils/issues/198#issuecomment-723145383 | https://api.github.com/repos/simonw/sqlite-utils/issues/198 | MDEyOklzc3VlQ29tbWVudDcyMzE0NTM4Mw== | simonw 9599 | 2020-11-06T15:36:47Z | 2020-11-06T15:36:47Z | OWNER | Should I register the custom |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support order by relevance against FTS4 737476423 | |
723144893 | https://github.com/simonw/sqlite-utils/issues/198#issuecomment-723144893 | https://api.github.com/repos/simonw/sqlite-utils/issues/198 | MDEyOklzc3VlQ29tbWVudDcyMzE0NDg5Mw== | simonw 9599 | 2020-11-06T15:35:45Z | 2020-11-06T15:35:45Z | OWNER | Here's a demo of that rank query. I had to sort by https://datasette-sqlite-fts4.datasette.io/24ways-fts4?sql=with+original+as+(%0D%0A++++select%0D%0A++++++++rowid%2C%0D%0A++++++++%0D%0A++++from+[articles]%0D%0A)%0D%0Aselect%0D%0A++++original.%2C%0D%0A++++rank_bm25(matchinfo([articles_fts]%2C+%27pcnalx%27))+as+rank%0D%0Afrom%0D%0A++++[original]%0D%0A++++join+[articles_fts]+on+[original].rowid+%3D+[articles_fts].rowid%0D%0Awhere%0D%0A++++[articles_fts]+match+%3Aquery%0D%0Aorder+by%0D%0A++++rank%0D%0Alimit+20&query=jquery+maps |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support order by relevance against FTS4 737476423 | |
723143633 | https://github.com/simonw/sqlite-utils/issues/198#issuecomment-723143633 | https://api.github.com/repos/simonw/sqlite-utils/issues/198 | MDEyOklzc3VlQ29tbWVudDcyMzE0MzYzMw== | simonw 9599 | 2020-11-06T15:33:12Z | 2020-11-06T15:33:12Z | OWNER | Here's the FTS5 query:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support order by relevance against FTS4 737476423 | |
722895825 | https://github.com/simonw/sqlite-utils/issues/198#issuecomment-722895825 | https://api.github.com/repos/simonw/sqlite-utils/issues/198 | MDEyOklzc3VlQ29tbWVudDcyMjg5NTgyNQ== | simonw 9599 | 2020-11-06T06:29:17Z | 2020-11-06T06:29:17Z | OWNER | I released a 1.0 (and 1.0.1) version of https://github.com/simonw/sqlite-fts4 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support order by relevance against FTS4 737476423 |
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 >30