issue_comments
21 rows where "updated_at" is on date 2022-03-11
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions, issue
created_at (date) 1 ✖
- 2022-03-11 21
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1065245831 | https://github.com/simonw/sqlite-utils/issues/413#issuecomment-1065245831 | https://api.github.com/repos/simonw/sqlite-utils/issues/413 | IC_kwDOCGYnMM4_flyH | simonw 9599 | 2022-03-11T15:59:14Z | 2022-03-11T15:59:14Z | OWNER | Hint from https://twitter.com/AdamChainz/status/1502311047612575745 > Try: > > `autodoc_typehints = 'description'` > > For a list-of-arguments format > > https://sphinx-doc.org/en/master/usage/extensions/autodoc.html#confval-autodoc_typehints | {"total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Display autodoc type information more legibly 1166587040 | |
1065247619 | https://github.com/simonw/sqlite-utils/issues/413#issuecomment-1065247619 | https://api.github.com/repos/simonw/sqlite-utils/issues/413 | IC_kwDOCGYnMM4_fmOD | simonw 9599 | 2022-03-11T16:01:20Z | 2022-03-11T16:01:20Z | OWNER | Definitely an improvement! <img width="658" alt="image" src="https://user-images.githubusercontent.com/9599/157903133-999ee5f8-9f0c-44de-b0f5-817cad6b2651.png"> It does highlight that I'm not currently using the `:param XXX: description` syntax though, which should move my descriptions of each parameter into that generated list. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Display autodoc type information more legibly 1166587040 | |
1065249883 | https://github.com/simonw/sqlite-utils/issues/413#issuecomment-1065249883 | https://api.github.com/repos/simonw/sqlite-utils/issues/413 | IC_kwDOCGYnMM4_fmxb | simonw 9599 | 2022-03-11T16:03:35Z | 2022-03-11T16:03:35Z | OWNER | Applying this change fixes that: ```diff diff --git a/sqlite_utils/db.py b/sqlite_utils/db.py index 3bc528f..2a79711 100644 --- a/sqlite_utils/db.py +++ b/sqlite_utils/db.py @@ -2293,18 +2293,18 @@ class Table(Queryable): """ Apply conversion function ``fn`` to every value in the specified columns. - - ``columns`` - a single column or list of string column names to convert. - - ``fn`` - a callable that takes a single argument, ``value``, and returns it converted. - - ``output`` - optional string column name to write the results to (defaults to the input column). - - ``output_type`` - if the output column needs to be created, this is the type that will be used + :param columns: a single column or list of string column names to convert. + :param fn: a callable that takes a single argument, ``value``, and returns it converted. + :param output: optional string column name to write the results to (defaults to the input column). + :param output_type: if the output column needs to be created, this is the type that will be used for the new column. - - ``drop`` - boolean, should the original column be dropped once the conversion is complete? - - ``multi`` - boolean, if ``True`` the return value of ``fn(value)`` will be expected to be a + :param drop: boolean, should the original column be dropped once the conversion is complete? + :param multi: boolean, if ``True`` the return value of ``fn(value)`` will be expected to be a dictionary, and new columns will be created for each key of that dictionary. - - ``where`` - a SQL fragment to use as a ``WHERE`` clause to limit the rows to which the conversion + :param where: a SQL fragment to use as a ``WHERE`` clause to limit the rows to which the conversion is applied, for example ``age > ?`` or ``age > :age``. - - ``where_args`` - a list of arguments (if using ``?``) or a dictionary (if using ``:ag… | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Display autodoc type information more legibly 1166587040 | |
1065334891 | https://github.com/simonw/datasette/issues/1634#issuecomment-1065334891 | https://api.github.com/repos/simonw/datasette/issues/1634 | IC_kwDOBm6k_c4_f7hr | dholth 208018 | 2022-03-11T17:38:08Z | 2022-03-11T17:38:08Z | NONE | I noticed the image was large when using fly. Is it possible to use a -slim base? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Update Dockerfile generated by `datasette publish` 1131295060 | |
1065345515 | https://github.com/simonw/sqlite-utils/issues/413#issuecomment-1065345515 | https://api.github.com/repos/simonw/sqlite-utils/issues/413 | IC_kwDOCGYnMM4_f-Hr | simonw 9599 | 2022-03-11T17:52:22Z | 2022-03-11T17:52:22Z | OWNER | Well this is a huge improvement! https://sqlite-utils.datasette.io/en/latest/reference.html#sqlite_utils.db.Table.insert <img width="714" alt="image" src="https://user-images.githubusercontent.com/9599/157922673-3377cc75-d52a-4e86-acac-c5b5b6ddade6.png"> I'm not crazy about the `extracts=<sqlite_utils.db.Default object>` thing though - I wonder if there's a neat way to customize that to be less verbose? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Display autodoc type information more legibly 1166587040 | |
1065357081 | https://github.com/simonw/sqlite-utils/issues/413#issuecomment-1065357081 | https://api.github.com/repos/simonw/sqlite-utils/issues/413 | IC_kwDOCGYnMM4_gA8Z | simonw 9599 | 2022-03-11T18:07:10Z | 2022-03-11T18:07:10Z | OWNER | I'm really happy with this improvement. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Display autodoc type information more legibly 1166587040 | |
1065377926 | https://github.com/simonw/sqlite-utils/issues/414#issuecomment-1065377926 | https://api.github.com/repos/simonw/sqlite-utils/issues/414 | IC_kwDOCGYnMM4_gGCG | simonw 9599 | 2022-03-11T18:34:05Z | 2022-03-11T18:34:05Z | OWNER | Two options: - Delete and recreate the release on GitHub, triggering it to be fixed on Read The Docs (as the `stable` version) - but cancel the push to PyPI, since that platform doesn't allow package versions to be over-written and in this case since the changelog file isn't included in the PyPI package there should be no change at all - Push a 3.25.2 release. I'm going to try and do that first option. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | I forgot to include the changelog in the 3.25.1 release 1166731361 | |
1065378902 | https://github.com/simonw/sqlite-utils/issues/414#issuecomment-1065378902 | https://api.github.com/repos/simonw/sqlite-utils/issues/414 | IC_kwDOCGYnMM4_gGRW | simonw 9599 | 2022-03-11T18:35:26Z | 2022-03-11T18:35:26Z | OWNER | I deleted both the release and the tag from GitHub using the web interface. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | I forgot to include the changelog in the 3.25.1 release 1166731361 | |
1065379528 | https://github.com/simonw/sqlite-utils/issues/414#issuecomment-1065379528 | https://api.github.com/repos/simonw/sqlite-utils/issues/414 | IC_kwDOCGYnMM4_gGbI | simonw 9599 | 2022-03-11T18:36:17Z | 2022-03-11T18:36:17Z | OWNER | I created a new tag and release: https://github.com/simonw/sqlite-utils/releases/tag/3.25.1 And I cancelled the publish workflow: https://github.com/simonw/sqlite-utils/actions/runs/1970415399 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | I forgot to include the changelog in the 3.25.1 release 1166731361 | |
1065380286 | https://github.com/simonw/sqlite-utils/issues/414#issuecomment-1065380286 | https://api.github.com/repos/simonw/sqlite-utils/issues/414 | IC_kwDOCGYnMM4_gGm- | simonw 9599 | 2022-03-11T18:37:23Z | 2022-03-11T18:37:23Z | OWNER | On ReadTheDocs that triggered a new `stable` build but it didn't seem to trigger a new build of `3.25.1`: https://readthedocs.org/projects/sqlite-utils/builds/ <img width="844" alt="image" src="https://user-images.githubusercontent.com/9599/157931210-80505416-509d-4c28-a894-b3f856ce0661.png"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | I forgot to include the changelog in the 3.25.1 release 1166731361 | |
1065381047 | https://github.com/simonw/sqlite-utils/issues/414#issuecomment-1065381047 | https://api.github.com/repos/simonw/sqlite-utils/issues/414 | IC_kwDOCGYnMM4_gGy3 | simonw 9599 | 2022-03-11T18:38:27Z | 2022-03-11T18:38:27Z | OWNER | OK that fixed it here: https://sqlite-utils.datasette.io/en/stable/changelog.html I'm going to trigger a rebuild of `3.25.1` too: <img width="881" alt="CleanShot 2022-03-11 at 10 37 33@2x" src="https://user-images.githubusercontent.com/9599/157931383-24682894-90be-4ede-b316-18efadbaf84b.png"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | I forgot to include the changelog in the 3.25.1 release 1166731361 | |
1065382145 | https://github.com/simonw/sqlite-utils/issues/414#issuecomment-1065382145 | https://api.github.com/repos/simonw/sqlite-utils/issues/414 | IC_kwDOCGYnMM4_gHEB | simonw 9599 | 2022-03-11T18:39:05Z | 2022-03-11T18:39:05Z | OWNER | https://sqlite-utils.datasette.io/en/3.25.1/changelog.html is currently wrong: <img width="971" alt="image" src="https://user-images.githubusercontent.com/9599/157931484-479f04ea-700c-4daf-8b63-10f3d8d40a94.png"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | I forgot to include the changelog in the 3.25.1 release 1166731361 | |
1065384183 | https://github.com/simonw/sqlite-utils/issues/414#issuecomment-1065384183 | https://api.github.com/repos/simonw/sqlite-utils/issues/414 | IC_kwDOCGYnMM4_gHj3 | simonw 9599 | 2022-03-11T18:40:39Z | 2022-03-11T18:40:39Z | OWNER | That fixed it: <img width="971" alt="image" src="https://user-images.githubusercontent.com/9599/157931695-383a0454-127e-4978-8888-eeccae0b40ad.png"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | I forgot to include the changelog in the 3.25.1 release 1166731361 | |
1065386352 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065386352 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_gIFw | simonw 9599 | 2022-03-11T18:41:37Z | 2022-03-11T18:41:37Z | OWNER | I like `add-generated-column` - feels very clear to me, and is a nice place for adding logic that checks if the DB version supports it or not and shows a useful error. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 | |
1065389386 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065389386 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_gI1K | simonw 9599 | 2022-03-11T18:42:53Z | 2022-03-11T21:40:51Z | OWNER | The Python API could be: ```python db[table_name].add_generated_column("field", str, "json_extract(data, '$.field')", stored=True) ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 | |
1065402557 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065402557 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_gMC9 | simonw 9599 | 2022-03-11T19:01:08Z | 2022-03-11T21:42:25Z | OWNER | Just spotted this in https://www.sqlite.org/gencol.html > The only functional difference is that one cannot add new STORED columns using the [ALTER TABLE ADD COLUMN](https://www.sqlite.org/lang_altertable.html#altertabaddcol) command. Only VIRTUAL columns can be added using ALTER TABLE. So to add stored columns to an existing table we would need to use the `.transform()` trick. Which implies that this should actually be a capability of the various `.create()` methods, since transform works by creating a new table with those and then copying across the old data. Here's where `.transform()` calls `.create_table_sql()` under the hood: https://github.com/simonw/sqlite-utils/blob/9388edf57aa15719095e3cf0952c1653cd070c9b/sqlite_utils/db.py#L1627-L1637 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 | |
1065440445 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065440445 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_gVS9 | simonw 9599 | 2022-03-11T19:52:15Z | 2022-03-11T19:52:15Z | OWNER | Two new parameters to `.create_table()` and friends: - `generated={...}` - generated column definitions - `generated_stored={...}` generated stored column definitions These columns will be added at the end of the table, but you can use the `column_order=` parameter to apply a different order. | {"total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 1, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 | |
1065458729 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065458729 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_gZwp | simonw 9599 | 2022-03-11T19:58:50Z | 2022-03-11T20:00:25Z | OWNER | I'm coming round to your suggestion to have this as extra arguments to `sqlite-utils add-column` now, especially since you also need to pass a column type. I'd like to come up with syntax for `sqlite-utils create-table` as well. https://sqlite-utils.datasette.io/en/stable/cli-reference.html#create-table Maybe extra `--generated-stored colname expression` (and `--generated`) options would work there. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 | |
1065477258 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065477258 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_geSK | eyeseast 25778 | 2022-03-11T20:14:59Z | 2022-03-11T20:14:59Z | CONTRIBUTOR | Good call on adding this to `create-table`, especially for stored columns. Having the stored/virtual split might make this tricky to implement, but I haven't gone any farther than thinking about what the CLI looks like. I'm going to try making the SQL side work first and figure that'll tell me more about what it needs. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 | |
1065596417 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065596417 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_g7YB | simonw 9599 | 2022-03-11T22:30:15Z | 2022-03-11T22:30:15Z | OWNER | I tried it out in Jupyter and it works as advertised: <img width="1076" alt="image" src="https://user-images.githubusercontent.com/9599/157980825-b362a162-b774-4fb5-8ec0-a7f539e62bd7.png"> Introspection is a bit weird: there doesn't seem to be a way to introspect generated columns outside of parsing the stored SQL schema for the columns at the moment! And the `.columns` method doesn't return them at all: https://github.com/simonw/sqlite-utils/blob/433813612ff9b4b501739fd7543bef0040dd51fe/sqlite_utils/db.py#L1207-L1213 Here's why: ``` >>> db.execute("PRAGMA table_info('t')").fetchall() [(0, 'body', 'TEXT', 0, None, 0)] >>> db.execute("PRAGMA table_xinfo('t')").fetchall() [(0, 'body', 'TEXT', 0, None, 0, 0), (1, 'd', 'INT', 0, None, 0, 2)] ``` So `table_xinfo()` is needed to get back columns including generated columns: https://www.sqlite.org/pragma.html#pragma_table_xinfo > **PRAGMA** *schema.***table_xinfo(***table-name***);** > > This pragma returns one row for each column in the named table, including [hidden columns](https://www.sqlite.org/vtab.html#hiddencol) in virtual tables. The output is the same as for [PRAGMA table_info](https://www.sqlite.org/pragma.html#pragma_table_info) except that hidden columns are shown rather than being omitted. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 | |
1065597709 | https://github.com/simonw/sqlite-utils/issues/411#issuecomment-1065597709 | https://api.github.com/repos/simonw/sqlite-utils/issues/411 | IC_kwDOCGYnMM4_g7sN | simonw 9599 | 2022-03-11T22:32:43Z | 2022-03-11T22:32:43Z | OWNER | Trying to figure out what that extra field in `table_info` compared to `table_xinfo` is: ``` >>> list(db.query("PRAGMA table_xinfo('t')")) [{'cid': 0, 'name': 'body', 'type': 'TEXT', 'notnull': 0, 'dflt_value': None, 'pk': 0, 'hidden': 0}, {'cid': 1, 'name': 'd', 'type': 'INT', 'notnull': 0, 'dflt_value': None, 'pk': 0, 'hidden': 2}] `` Presumably `hidden` 0 v.s 2 v.s. other values has meaning. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support for generated columns 1160034488 |
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 3 ✖