home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

5 rows where issue = 1166587040 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • simonw 5

issue 1

  • Display autodoc type information more legibly · 5 ✖

author_association 1

  • OWNER 5
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
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  
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

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  
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 functionfn`` 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 :age).
    • show_progress - boolean, should a progress bar be displayed?
  • :param where_args: a list of arguments (if using ?) or a dictionary (if using :age).
  • :param show_progress: boolean, should a progress bar be displayed?
     See :ref:`python_api_convert`.
     """
    

    ```

{
    "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  
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!

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  
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  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

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]);
Powered by Datasette · Queries took 25.492ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows