issue_comments

Table actions

8 rows where author_association = "OWNER", "created_at" is on date 2021-01-24 and user = 9599 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

  • simonw · 8 ✖

author_association 1

  • OWNER · 8 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
766463496 https://github.com/simonw/datasette/issues/1090#issuecomment-766463496 https://api.github.com/repos/simonw/datasette/issues/1090 MDEyOklzc3VlQ29tbWVudDc2NjQ2MzQ5Ng== simonw 9599 2021-01-24T23:57:00Z 2021-01-24T23:57:00Z OWNER

Related: I built datasette-leaflet-freedraw which turns any canned query field called freedraw or something_freedraw into an interactive map that you can draw on to create a GeoJSON MultiPolygon.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Custom widgets for canned query forms 741862364  
766462475 https://github.com/simonw/datasette/issues/1202#issuecomment-766462475 https://api.github.com/repos/simonw/datasette/issues/1202 MDEyOklzc3VlQ29tbWVudDc2NjQ2MjQ3NQ== simonw 9599 2021-01-24T23:49:28Z 2021-01-24T23:50:33Z OWNER

Can use an "admonition" similar to this: sphinx .. warning:: Restricting access to tables and views in this way will NOT prevent users from querying them using arbitrary SQL queries, `like this <https://latest.datasette.io/fixtures?sql=select+*+from+facetable>`__ for example. As seen on https://docs.datasette.io/en/stable/authentication.html#controlling-access-to-specific-tables-and-views

Documentation: https://docutils.sourceforge.io/docs/ref/rst/directives.html#specific-admonitions

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Documentation convention for marking unstable APIs. 792931244  
766462197 https://github.com/simonw/datasette/issues/1154#issuecomment-766462197 https://api.github.com/repos/simonw/datasette/issues/1154 MDEyOklzc3VlQ29tbWVudDc2NjQ2MjE5Nw== simonw 9599 2021-01-24T23:47:06Z 2021-01-24T23:47:06Z OWNER

I'm going to document this but mark it as unstable, using a new documentation convention for marking unstable APIs.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Documentation for new _internal database and tables 771208009  
766434629 https://github.com/simonw/datasette/issues/1179#issuecomment-766434629 https://api.github.com/repos/simonw/datasette/issues/1179 MDEyOklzc3VlQ29tbWVudDc2NjQzNDYyOQ== simonw 9599 2021-01-24T21:23:47Z 2021-01-24T21:23:47Z OWNER

I'm just going to do path and full_path (which includes the querystring). Thedatasette.absolute_url()` method can be used by plugins that need the full URL.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Make original path available to render hooks 780278550  
766433153 https://github.com/simonw/datasette/issues/1190#issuecomment-766433153 https://api.github.com/repos/simonw/datasette/issues/1190 MDEyOklzc3VlQ29tbWVudDc2NjQzMzE1Mw== simonw 9599 2021-01-24T21:13:25Z 2021-01-24T21:13:25Z OWNER

This ties in to a bunch of other ideas that are in flight at the moment.

If you're publishing databases by uploading them, how do you attach metadata? Ideally by baking it into the database file itself, using the mechanism from #1169.

How could this interact with the datasette insert concept from #1163? Could you pass a CSV file to the upload command and have that converted and uploaded for you, or would you create the database file locally using datasette insert and then upload it as a separate datasette upload step?

Lots to think about here.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `datasette publish upload` mechanism for uploading databases to an existing Datasette instance 787098146  
766430644 https://github.com/simonw/datasette/issues/1190#issuecomment-766430644 https://api.github.com/repos/simonw/datasette/issues/1190 MDEyOklzc3VlQ29tbWVudDc2NjQzMDY0NA== simonw 9599 2021-01-24T20:57:03Z 2021-01-24T20:57:03Z OWNER

I really like this idea. It feels like an opportunity for a plugin that adds two things: an API endpoint to Datasette for accepting uploaded databases, and a datasette publish upload subcommand which can upload files to that endpoint (with some kind of authentication mechanism).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `datasette publish upload` mechanism for uploading databases to an existing Datasette instance 787098146  
766430111 https://github.com/simonw/datasette/issues/1197#issuecomment-766430111 https://api.github.com/repos/simonw/datasette/issues/1197 MDEyOklzc3VlQ29tbWVudDc2NjQzMDExMQ== simonw 9599 2021-01-24T20:53:40Z 2021-01-24T20:53:40Z OWNER

https://devcenter.heroku.com/articles/slug-compiler#slug-size says that the maximum allowed size is 500MB - my hunch is that the Datasette application itself weighs in at only a dozen or so MB but I haven't measured it. So I would imagine anything up to around 450MB should work OK on Heroku.

Cloud Run works for up to about 2GB in my experience.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 DB size limit for publishing with Heroku 791381623  
766428183 https://github.com/simonw/datasette/issues/1198#issuecomment-766428183 https://api.github.com/repos/simonw/datasette/issues/1198 MDEyOklzc3VlQ29tbWVudDc2NjQyODE4Mw== simonw 9599 2021-01-24T20:40:37Z 2021-01-24T20:40:37Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Plugin testing documentation on using pytest-httpx 792625812  

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