issues

Table actions

3 rows where state = "closed" and user = 418191 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

state 1

  • closed · 3 ✖

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
541331755 MDExOlB1bGxSZXF1ZXN0MzU2MDA0MjQy 653 allow leading comments in SQL input field jaywgraves 418191 closed 0     8 2019-12-21T14:19:52Z 2020-02-05T02:35:41Z 2020-02-05T02:13:25Z CONTRIBUTOR simonw/datasette/pulls/653

this changes the SQL validation to allow for lines that are commented out

my main use case for this is that I like to write a succession of queries when trying to solve a problem. In most native SQL clients there is a key binding that will run just the current highlighted query or the program is smart enough to run just the query that the cursor is in if it's properly delimited with a ';'. Typically my workflow will start with a single simple query and I'll copy/paste it to a new query below when I want to make big changes while debugging. This makes it easy to go back to a working version above when the query doesn't work. Since datasette sends the whole query to the DB I have to comment out the older queries by prefixing each line with --. This gets caught by the validators when I use my typical strategy of copy/pasting each successive query below the last one.
so this is just a simple fix to allow for a query to be sent to the DB with leading comments.

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/653/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
386459810 MDExOlB1bGxSZXF1ZXN0MjM1MTk0Mjg2 390 tiny typo in customization docs jaywgraves 418191 closed 0     1 2018-12-01T13:44:42Z 2019-12-19T02:30:35Z 2018-12-16T21:32:56Z CONTRIBUTOR simonw/datasette/pulls/390

was looking to add some custom templates to my use of datasette and saw this small typo.

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/390/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
361764460 MDExOlB1bGxSZXF1ZXN0MjE2NjUxMzE3 365 fix small doc typo jaywgraves 418191 closed 0     2 2018-09-19T14:02:02Z 2019-12-19T02:30:33Z 2018-09-19T17:15:43Z CONTRIBUTOR simonw/datasette/pulls/365
datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/365/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT, [performed_via_github_app] TEXT, [reactions] TEXT, [draft] INTEGER, [state_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);