issues

Table actions

7 rows where repo = 107914493, state = "closed" and user = 2657547 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 2

state 1

  • closed · 7 ✖

repo 1

  • datasette · 7 ✖
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
620969465 MDU6SXNzdWU2MjA5Njk0NjU= 767 Allow to specify a URL fragment for canned queries rixx 2657547 closed 0   Datasette 0.43 5471110 2 2020-05-19T13:17:42Z 2020-05-27T21:52:25Z 2020-05-27T21:52:25Z CONTRIBUTOR  

Canned queries are very useful to direct users to prepared data and views. I like to use them with charts using datasette-vega a lot, because people get a direct impression at first glance.

datasette-vega doesn't show up by default though, and users have to click through to it. Also, datasette-vega does not always guess the best way to render columns correctly though, so it would be nice if I could specify a URL fragment in my canned queries to make sure people see what I want them to see.

My current workaround is to include a fragement link in description_html and ask people to reload the page, like here, which is a bit hacky.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/767/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
505818256 MDExOlB1bGxSZXF1ZXN0MzI3MTcyNTQ1 590 Handle spaces in DB names rixx 2657547 closed 0     3 2019-10-11T12:18:22Z 2019-11-04T23:16:31Z 2019-11-04T23:16:30Z CONTRIBUTOR simonw/datasette/pulls/590

Closes #503

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/590/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
509535510 MDExOlB1bGxSZXF1ZXN0MzMwMDc2MjYz 602 Offer to format readonly SQL rixx 2657547 closed 0     3 2019-10-20T02:29:32Z 2019-11-04T07:29:33Z 2019-11-04T02:39:56Z CONTRIBUTOR simonw/datasette/pulls/602

Following discussion in #601, this PR adds a "Format SQL" button to read-only SQL (if the SQL actually differs from the formatting result).

It also removes a console error on readonly SQL queries.

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/602/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
505814865 MDExOlB1bGxSZXF1ZXN0MzI3MTY5NzQ4 589 Display metadata footer on custom SQL queries rixx 2657547 closed 0     0 2019-10-11T12:10:28Z 2019-10-14T08:58:23Z 2019-10-14T03:53:22Z CONTRIBUTOR simonw/datasette/pulls/589

Closes #408

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/589/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
505837199 MDExOlB1bGxSZXF1ZXN0MzI3MTg4MDg3 591 Sort databases on homepage by argument order rixx 2657547 closed 0     1 2019-10-11T12:57:38Z 2019-10-14T08:57:50Z 2019-10-14T03:52:34Z CONTRIBUTOR simonw/datasette/pulls/591

Closes #585

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/591/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
505950145 MDExOlB1bGxSZXF1ZXN0MzI3Mjc5ODE4 592 Offer SQL formatting rixx 2657547 closed 0     1 2019-10-11T16:35:49Z 2019-10-14T08:57:12Z 2019-10-14T03:46:13Z CONTRIBUTOR simonw/datasette/pulls/592

SQL code will be formatted on page load, and can additionally be formatted by clicking the "Format SQL" button. Closes #136

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/592/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
459627549 MDU6SXNzdWU0NTk2Mjc1NDk= 523 Show total/unfiltered row count when filtering rixx 2657547 closed 0     2 2019-06-23T22:56:48Z 2019-06-24T01:38:14Z 2019-06-24T01:38:14Z CONTRIBUTOR  

When I'm seeing a filtered view of a table, I'd like to be able to see something like '2 rows where status != "closed" (of 1000 total)' to have a context for the data I'm seeing – e.g. currently my database is being filled by an importer, so this information would be super helpful.

Since this information would be a performance hit, maybe something like '12 rows where status != "closed" (of ??? total)' with lazy-loading on-click(?) could be applied (Or via a "How many total?" tooltip, or …)

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/523/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed

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