issue_comments

4 rows where user = 418191 sorted by updated_at descending

View and edit SQL

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

user

  • jaywgraves · 4

author_association

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue
582106085 https://github.com/simonw/datasette/pull/653#issuecomment-582106085 https://api.github.com/repos/simonw/datasette/issues/653 MDEyOklzc3VlQ29tbWVudDU4MjEwNjA4NQ== jaywgraves 418191 2020-02-04T20:43:43Z 2020-02-04T20:43:43Z CONTRIBUTOR

but this also doesn't have to land at all if it doesn't match your use case.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
allow leading comments in SQL input field 541331755
582105810 https://github.com/simonw/datasette/pull/653#issuecomment-582105810 https://api.github.com/repos/simonw/datasette/issues/653 MDEyOklzc3VlQ29tbWVudDU4MjEwNTgxMA== jaywgraves 418191 2020-02-04T20:43:01Z 2020-02-04T20:43:01Z CONTRIBUTOR

I think the existing code will be OK even if I strip the lines in the middle of a new line delimited string.

It's only used for the validation, SQLite handles the -- just fine and the whole SQL textarea still gets sent once it passes validation.

I can add your test case to my branch later this evening though.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
allow leading comments in SQL input field 541331755
422915450 https://github.com/simonw/datasette/issues/329#issuecomment-422915450 https://api.github.com/repos/simonw/datasette/issues/329 MDEyOklzc3VlQ29tbWVudDQyMjkxNTQ1MA== jaywgraves 418191 2018-09-19T18:45:02Z 2018-09-20T10:50:50Z CONTRIBUTOR

That works for me. Was able to pull the public image and no errors on my canned query. (~although a small rendering bug. I'll create an issue and if I have time today, a PR to fix~ this turned out to be my error.)
Thanks for the quick response!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Travis should push tagged images to Docker Hub for each release 336465018
422821483 https://github.com/simonw/datasette/issues/329#issuecomment-422821483 https://api.github.com/repos/simonw/datasette/issues/329 MDEyOklzc3VlQ29tbWVudDQyMjgyMTQ4Mw== jaywgraves 418191 2018-09-19T14:17:42Z 2018-09-19T14:17:42Z CONTRIBUTOR

I'm using the docker image (0.23.2) and notice some differences/bugs between the docs and the published version with canned queries. (submitted a tiny doc fix also)

I was able to build the docker container locally using master and I'm using that for now.
Would it be possible to manually push 0.24 to DockerHub until the TravisCI stuff is fixed?

I would like to run this in our Kubernetes cluster but don't want to publish a version in our internal registry if I don't have to.
Thanks!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Travis should push tagged images to Docker Hub for each release 336465018

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])
);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);
Powered by Datasette · Query took 21.55ms · About: github-to-sqlite