issue_comments

Table actions

14 rows where "created_at" is on date 2017-12-10 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
350527283 https://github.com/simonw/datasette/issues/121#issuecomment-350527283 https://api.github.com/repos/simonw/datasette/issues/121 MDEyOklzc3VlQ29tbWVudDM1MDUyNzI4Mw== simonw 9599 2017-12-10T06:00:47Z 2017-12-10T06:00:47Z OWNER

This is also really interesting when combined with the spatialite AsGeoJSON function: http://www.gaia-gis.it/gaia-sins/spatialite-sql-4.2.0.html#p3misc

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 ?_json=foo&_json=bar query string argument  275089535  
350521853 https://github.com/simonw/datasette/issues/123#issuecomment-350521853 https://api.github.com/repos/simonw/datasette/issues/123 MDEyOklzc3VlQ29tbWVudDM1MDUyMTg1Mw== simonw 9599 2017-12-10T03:09:53Z 2017-12-10T03:09:53Z OWNER

I'm going to keep this separate in csvs-to-sqlite.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Datasette serve should accept paths/URLs to CSVs and other file formats 275125561  
350521806 https://github.com/simonw/datasette/issues/138#issuecomment-350521806 https://api.github.com/repos/simonw/datasette/issues/138 MDEyOklzc3VlQ29tbWVudDM1MDUyMTgwNg== simonw 9599 2017-12-10T03:08:26Z 2017-12-10T03:08:36Z OWNER

Implemented this in 80bf3afa43e3cb396c7a7c9b168eedbc6fe0fa15 and #165. Didn't use data package though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Per-database and per-table metadata, probably using data-package 275476839  
350521780 https://github.com/simonw/datasette/issues/91#issuecomment-350521780 https://api.github.com/repos/simonw/datasette/issues/91 MDEyOklzc3VlQ29tbWVudDM1MDUyMTc4MA== simonw 9599 2017-12-10T03:07:53Z 2017-12-10T03:07:53Z OWNER

Won't fix - I think the custom templates and static stuff in https://github.com/simonw/datasette/releases/tag/0.14 renders this obsolete.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to serve databases from a different prefix, serve regular content elsewhere 273878873  
350521736 https://github.com/simonw/datasette/issues/90#issuecomment-350521736 https://api.github.com/repos/simonw/datasette/issues/90 MDEyOklzc3VlQ29tbWVudDM1MDUyMTczNg== simonw 9599 2017-12-10T03:06:34Z 2017-12-10T03:06:34Z OWNER

Heroku is now in the README as of 6bdfcf60760c27e29ff34692d06e62b36aeecc56

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 datasette publish heroku 273846123  
350521711 https://github.com/simonw/datasette/issues/90#issuecomment-350521711 https://api.github.com/repos/simonw/datasette/issues/90 MDEyOklzc3VlQ29tbWVudDM1MDUyMTcxMQ== simonw 9599 2017-12-10T03:05:48Z 2017-12-10T03:05:48Z OWNER

I fixed that last issue in c195ee4d46f2577b1943836a8270d84c8341d138

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 datasette publish heroku 273846123  
350521635 https://github.com/simonw/datasette/issues/52#issuecomment-350521635 https://api.github.com/repos/simonw/datasette/issues/52 MDEyOklzc3VlQ29tbWVudDM1MDUyMTYzNQ== simonw 9599 2017-12-10T03:02:56Z 2017-12-10T03:02:56Z OWNER

I don't think this is necessary.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Solution for temporarily uploading DB so it can be built by docker 273026602  
350521619 https://github.com/simonw/datasette/issues/42#issuecomment-350521619 https://api.github.com/repos/simonw/datasette/issues/42 MDEyOklzc3VlQ29tbWVudDM1MDUyMTYxOQ== simonw 9599 2017-12-10T03:02:14Z 2017-12-10T03:02:14Z OWNER

I think the datasette skeleton command from #164 makes this obsolete.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Homepage UI for editing metadata file 268591332  
350519821 https://github.com/simonw/datasette/issues/153#issuecomment-350519821 https://api.github.com/repos/simonw/datasette/issues/153 MDEyOklzc3VlQ29tbWVudDM1MDUxOTgyMQ== simonw 9599 2017-12-10T02:08:45Z 2017-12-10T02:08:45Z OWNER

Also worth mentioning: as of #160 and #157 the datasette publish now, datasette publish heroku and datasette package commands all know how to bundle up any --static or --template-dir content and include it in the Docker image / Heroku/Now deployment that gets generated.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to customize presentation of specific columns in HTML view 276842536  
350519736 https://github.com/simonw/datasette/issues/153#issuecomment-350519736 https://api.github.com/repos/simonw/datasette/issues/153 MDEyOklzc3VlQ29tbWVudDM1MDUxOTczNg== simonw 9599 2017-12-10T02:06:01Z 2017-12-10T02:06:01Z OWNER

@ftrain Datasette 0.14 is now released with all of the above: https://github.com/simonw/datasette/releases/tag/0.14

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to customize presentation of specific columns in HTML view 276842536  
350519711 https://github.com/simonw/datasette/issues/169#issuecomment-350519711 https://api.github.com/repos/simonw/datasette/issues/169 MDEyOklzc3VlQ29tbWVudDM1MDUxOTcxMQ== simonw 9599 2017-12-10T02:04:56Z 2017-12-10T02:04:56Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Release v0.14 with templates and static files features 280744309  
350516782 https://github.com/simonw/datasette/issues/167#issuecomment-350516782 https://api.github.com/repos/simonw/datasette/issues/167 MDEyOklzc3VlQ29tbWVudDM1MDUxNjc4Mg== simonw 9599 2017-12-10T00:48:54Z 2017-12-10T00:48:54Z OWNER

I can simplify this all by dropping the nicety where if a table is using a rowid the Link column is titled rowid instead.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Nasty bug: last column not being correctly displayed 280315352  
350515985 https://github.com/simonw/datasette/issues/167#issuecomment-350515985 https://api.github.com/repos/simonw/datasette/issues/167 MDEyOklzc3VlQ29tbWVudDM1MDUxNTk4NQ== simonw 9599 2017-12-10T00:28:39Z 2017-12-10T00:28:39Z OWNER

A better alternative:

async def display_columns_and_rows(self, database, table, rows, link_column=False):

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Nasty bug: last column not being correctly displayed 280315352  
350515616 https://github.com/simonw/datasette/issues/167#issuecomment-350515616 https://api.github.com/repos/simonw/datasette/issues/167 MDEyOklzc3VlQ29tbWVudDM1MDUxNTYxNg== simonw 9599 2017-12-10T00:21:58Z 2017-12-10T00:21:58Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Nasty bug: last column not being correctly displayed 280315352  

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