issue_comments

9 rows where user = 132978 sorted by updated_at descending

View and edit SQL

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

user

  • terrycojones · 9

author_association

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue
603849245 https://github.com/simonw/datasette/issues/394#issuecomment-603849245 https://api.github.com/repos/simonw/datasette/issues/394 MDEyOklzc3VlQ29tbWVudDYwMzg0OTI0NQ== terrycojones 132978 2020-03-25T13:48:13Z 2020-03-25T13:48:13Z NONE

Great - thanks again.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
base_url configuration setting 396212021
603539349 https://github.com/simonw/datasette/issues/394#issuecomment-603539349 https://api.github.com/repos/simonw/datasette/issues/394 MDEyOklzc3VlQ29tbWVudDYwMzUzOTM0OQ== terrycojones 132978 2020-03-24T22:33:23Z 2020-03-24T22:33:23Z NONE

Hi Simon - I'm just (trying, at least) to follow along in the above. I can't try it out now, but I will if no one else gets to it. Sorry I didn't write any tests in the original bit of code I pushed - I was just trying to see if it could work & whether you'd want to maybe head in that direction. Anyway, thank you, I will certainly use this. Comment back here if no one tried it out & I'll make time.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
base_url configuration setting 396212021
602916580 https://github.com/simonw/datasette/issues/394#issuecomment-602916580 https://api.github.com/repos/simonw/datasette/issues/394 MDEyOklzc3VlQ29tbWVudDYwMjkxNjU4MA== terrycojones 132978 2020-03-23T23:37:06Z 2020-03-23T23:37:06Z NONE

@simonw You're welcome - I was just trying it out back in December as I thought it should work. Now there's a pandemic to work on though.... so no time at all for more at the moment. BTW, I have datasette running on several protein and full (virus) genome databases I build, and it's great - thank you! Hi and best regards to you & Nat :-)

{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 1,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
base_url configuration setting 396212021
602911133 https://github.com/simonw/datasette/issues/394#issuecomment-602911133 https://api.github.com/repos/simonw/datasette/issues/394 MDEyOklzc3VlQ29tbWVudDYwMjkxMTEzMw== terrycojones 132978 2020-03-23T23:22:10Z 2020-03-23T23:22:10Z NONE

I just updated #652 to remove a merge conflict. I think it's an easy way to add this functionality. I don't have time to do more though, sorry!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
base_url configuration setting 396212021
567226048 https://github.com/simonw/datasette/issues/596#issuecomment-567226048 https://api.github.com/repos/simonw/datasette/issues/596 MDEyOklzc3VlQ29tbWVudDU2NzIyNjA0OA== terrycojones 132978 2019-12-18T21:43:13Z 2019-12-18T21:43:13Z NONE

Meant to add that of course it would be better not to reinvent CSS (one time was already enough). But one option would be to provide a mechanism to specify a CSS class for a column (a cell, a row...) and let the user give a URL path to a CSS file on the command line.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Handle really wide tables better 507454958
567225156 https://github.com/simonw/datasette/issues/596#issuecomment-567225156 https://api.github.com/repos/simonw/datasette/issues/596 MDEyOklzc3VlQ29tbWVudDU2NzIyNTE1Ng== terrycojones 132978 2019-12-18T21:40:35Z 2019-12-18T21:40:35Z NONE

I initially went looking for a way to hide a column completely. Today I found the setting to truncate cells, but it applies to all cells. In my case I have text columns that can have many thousands of characters. I was wondering whether the metadata JSON would be an appropriate place to indicate how columns are displayed (on a col-by-col basis). E.g., I'd like to be able to specify that only 20 chars of a given column be shown, and the font be monospace. But maybe I can do that in some other way - I barely know anything about datasette yet, sorry!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Handle really wide tables better 507454958
567219479 https://github.com/simonw/datasette/issues/394#issuecomment-567219479 https://api.github.com/repos/simonw/datasette/issues/394 MDEyOklzc3VlQ29tbWVudDU2NzIxOTQ3OQ== terrycojones 132978 2019-12-18T21:24:23Z 2019-12-18T21:24:23Z NONE

@simonw What about allowing a base url. The <base>....</base> tag has been around forever. Then just use all relative URLs, which I guess is likely what you already do. See https://www.w3schools.com/TAGs/tag_base.asp

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
base_url configuration setting 396212021
567128636 https://github.com/simonw/datasette/issues/394#issuecomment-567128636 https://api.github.com/repos/simonw/datasette/issues/394 MDEyOklzc3VlQ29tbWVudDU2NzEyODYzNg== terrycojones 132978 2019-12-18T17:19:46Z 2019-12-18T17:19:46Z NONE

Hmmm, wait, maybe my mindless (copy/paste) use of proxy_redirect is causing me grief...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
base_url configuration setting 396212021
567127981 https://github.com/simonw/datasette/issues/394#issuecomment-567127981 https://api.github.com/repos/simonw/datasette/issues/394 MDEyOklzc3VlQ29tbWVudDU2NzEyNzk4MQ== terrycojones 132978 2019-12-18T17:18:06Z 2019-12-18T17:18:06Z NONE

Agreed, this would be nice to have. I'm currently working around it in nginx with additional location blocks:

    location /datasette/ {
        proxy_pass         http://127.0.0.1:8001/;
        proxy_redirect     off;
        include proxy_params;
    }

    location /dna-protein-genome/ {
        proxy_pass         http://127.0.0.1:8001/dna-protein-genome/;
        proxy_redirect     off;
        include proxy_params;
    }

    location /rna-protein-genome/ {
        proxy_pass         http://127.0.0.1:8001/rna-protein-genome/;
        proxy_redirect     off;
        include proxy_params;
    }

The 2nd and 3rd above are my databases. This works, but I have a small problem with URLs like /rna-protein-genome?params.... that I could fix with some more nginx munging. I seem to do this sort of thing once every 5 years and then have to look it all up again.

Thanks!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
base_url configuration setting 396212021

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 41.801ms · About: github-to-sqlite