issue_comments

Table actions

3 rows where user = 870184 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

  • xrotwang · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
585285753 https://github.com/simonw/datasette/issues/667#issuecomment-585285753 https://api.github.com/repos/simonw/datasette/issues/667 MDEyOklzc3VlQ29tbWVudDU4NTI4NTc1Mw== xrotwang 870184 2020-02-12T16:18:22Z 2020-02-12T16:18:22Z NONE

@simonw fwiw, here's the plugin I implemented to support CLDF datasets: https://github.com/cldf/datasette-cldf/blob/master/README.md It's a bit of a hybrid in that it does both, building the SQLite database and extending datasette by exploting what we know about the data format - so it may not be worth listing it with the other plugins.

Having tools like datasette available definitely helps selling people on package formats like CLDF (or CSVW), many thanks for this!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Allow injecting configuration data from plugins 562787785  
585109972 https://github.com/simonw/datasette/issues/667#issuecomment-585109972 https://api.github.com/repos/simonw/datasette/issues/667 MDEyOklzc3VlQ29tbWVudDU4NTEwOTk3Mg== xrotwang 870184 2020-02-12T09:21:22Z 2020-02-12T09:21:22Z NONE

I think I found a better way to implement my use case: I wrap the datasette serve call into my own cli, which - creates the SQLite from CSV data - writes metadata.json for datasette - determines suitable config like max_page_size - then calls datasette serve.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Allow injecting configuration data from plugins 562787785  
584203999 https://github.com/simonw/datasette/issues/352#issuecomment-584203999 https://api.github.com/repos/simonw/datasette/issues/352 MDEyOklzc3VlQ29tbWVudDU4NDIwMzk5OQ== xrotwang 870184 2020-02-10T16:18:58Z 2020-02-10T16:18:58Z NONE

I don't want to re-open this issue, but I'm wondering whether it would be possible to include the full row for which a specific cell is to be rendered in the hook signature. My use case are rows where custom rendering would need access to multiple values (specifically, rows containing the constituents of interlinear glossed text (IGT) in separate columns, see https://github.com/cldf/cldf/tree/master/components/examples).

I could probably cobble this together with custom SQL and the sql-to-html plugin. But having a full row within a render_cell implementation seems a lot simpler.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 render_cell(value) plugin hook 345821500  

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