issue_comments

Table actions

10 rows where user = 198537 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • rgieseke · 10 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1812750369 https://github.com/simonw/datasette/pull/2209#issuecomment-1812750369 https://api.github.com/repos/simonw/datasette/issues/2209 IC_kwDOBm6k_c5sDGAh rgieseke 198537 2023-11-15T15:29:37Z 2023-11-15T15:29:37Z CONTRIBUTOR

Looks like tests are passing now but there is an issue with yaml loading and/or cog.

https://github.com/simonw/datasette/actions/runs/6879299298/job/18710911166?pr=2209

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Fix query for suggested facets with column named value 1994861266  
1812623778 https://github.com/simonw/datasette/pull/2209#issuecomment-1812623778 https://api.github.com/repos/simonw/datasette/issues/2209 IC_kwDOBm6k_c5sCnGi rgieseke 198537 2023-11-15T14:22:42Z 2023-11-15T15:24:09Z CONTRIBUTOR

Whoops, looks like I forgot to check for other places where the 'facetable' table is used in the tests.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Fix query for suggested facets with column named value 1994861266  
1812617851 https://github.com/simonw/datasette/issues/2208#issuecomment-1812617851 https://api.github.com/repos/simonw/datasette/issues/2208 IC_kwDOBm6k_c5sClp7 rgieseke 198537 2023-11-15T14:18:58Z 2023-11-15T14:18:58Z CONTRIBUTOR

Without aliases:

The proposed fix in #2209 also works when the 'value' column is actually facetable (just added another value in the 'value' column).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 No suggested facets when a column named 'value' is included 1994857251  
789186458 https://github.com/simonw/datasette/issues/1238#issuecomment-789186458 https://api.github.com/repos/simonw/datasette/issues/1238 MDEyOklzc3VlQ29tbWVudDc4OTE4NjQ1OA== rgieseke 198537 2021-03-02T20:19:30Z 2021-03-02T20:19:30Z CONTRIBUTOR

A custom templates/index.html seems to work and custom pages as a workaround with moving them to pages/base_url_dir.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Custom pages don't work with base_url setting 813899472  
391077700 https://github.com/simonw/datasette/pull/279#issuecomment-391077700 https://api.github.com/repos/simonw/datasette/issues/279 MDEyOklzc3VlQ29tbWVudDM5MTA3NzcwMA== rgieseke 198537 2018-05-22T17:38:17Z 2018-05-22T17:38:17Z CONTRIBUTOR

Alright, that should work now -- let me know if you would prefer any different behaviour.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add version number support with Versioneer 325352370  
391073267 https://github.com/simonw/datasette/pull/279#issuecomment-391073267 https://api.github.com/repos/simonw/datasette/issues/279 MDEyOklzc3VlQ29tbWVudDM5MTA3MzI2Nw== rgieseke 198537 2018-05-22T17:24:16Z 2018-05-22T17:24:16Z CONTRIBUTOR

Sorry, just realised you rely on version being a module ...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add version number support with Versioneer 325352370  
391073009 https://github.com/simonw/datasette/pull/279#issuecomment-391073009 https://api.github.com/repos/simonw/datasette/issues/279 MDEyOklzc3VlQ29tbWVudDM5MTA3MzAwOQ== rgieseke 198537 2018-05-22T17:23:26Z 2018-05-22T17:23:26Z CONTRIBUTOR

I think I prefer the aesthetics of just "0.22" for the version string if it's a tagged release with no additional changes - does that work?

Yes! That's the default versioneer behaviour.

I'd like to continue to provide a tuple that can be imported from the version.py module as well, as seen here:

Should work now, it can be a two (for a tagged version), three or four items tuple.

``` In [2]: datasette.version Out[2]: '0.12+292.ga70c2a8.dirty'

In [3]: datasette.version_info Out[3]: ('0', '12+292', 'ga70c2a8', 'dirty') ```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add version number support with Versioneer 325352370  
390250253 https://github.com/simonw/datasette/issues/273#issuecomment-390250253 https://api.github.com/repos/simonw/datasette/issues/273 MDEyOklzc3VlQ29tbWVudDM5MDI1MDI1Mw== rgieseke 198537 2018-05-18T15:49:52Z 2018-05-18T15:49:52Z CONTRIBUTOR

Shouldn't versioneer do that?

E.g. 0.21+2.g1076c97

You'd need to install via pip install git+https://github.com/simow/datasette.git though, this does a temp git clone.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Figure out a way to have /-/version return current git commit hash 324451322  
345652450 https://github.com/simonw/datasette/issues/27#issuecomment-345652450 https://api.github.com/repos/simonw/datasette/issues/27 MDEyOklzc3VlQ29tbWVudDM0NTY1MjQ1MA== rgieseke 198537 2017-11-20T10:19:39Z 2017-11-20T10:19:39Z CONTRIBUTOR

If Data Package metadata gets adopted (#105) the views spec work might also be worth a look:

http://frictionlessdata.io/specs/views/

http://datahub.io/docs/features/views

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to plot a simple graph 267886330  
345503897 https://github.com/simonw/datasette/issues/105#issuecomment-345503897 https://api.github.com/repos/simonw/datasette/issues/105 MDEyOklzc3VlQ29tbWVudDM0NTUwMzg5Nw== rgieseke 198537 2017-11-19T09:38:08Z 2017-11-19T09:38:08Z CONTRIBUTOR

Thanks, I wrote this very simple reader because the default approach as described on the Datahub pages seemed to complicated. I had metadata from the datapackage.json attached to the returned DataFrames but removed this due to some attribute handling change in the latest Pandas version.

This could also be useful for getting from Data Package to SQL db: https://github.com/frictionlessdata/tableschema-sql-py

I maintain a few climate science related dataset at https://github.com/openclimatedata/

The Data Retriever (mainly ecological data) by @ethanwhite et al. is also using the Data Package format for metadata and has some tooling for different dbs:

https://frictionlessdata.io/articles/the-data-retriever/ https://github.com/weecology/retriever

The Open Power System Data project also has a couple of datasets that show nicely how CSV is great for assembling and then already make SQLite files available. It's one of the first data sets I tried with Datasette, perfect for the use case of getting an API for putting power stations on a map ...

https://data.open-power-system-data.org/

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Consider data-package as a format for metadata 274314940  

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]);