issues

Table actions

8 rows where "created_at" is on date 2019-05-11 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

state 2

type 1

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
443040665 MDU6SXNzdWU0NDMwNDA2NjU= 466 Move "no such module: VirtualSpatialIndex" code elsewhere simonw 9599 closed 0   0.28 4305096 2 2019-05-11T22:09:00Z 2022-01-20T21:29:41Z 2019-05-11T22:57:22Z OWNER  

We currently show a useful warning (from #331) when the user tries to open a spatialite database without first loading the module:

https://github.com/simonw/datasette/blob/c692cd291111050483a32bea1ee08e994a0b781b/datasette/app.py#L547-L554

This code is part of .inspect() which is going away - see #462 - so I need to find somewhere else for it to live.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/466/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
443021509 MDU6SXNzdWU0NDMwMjE1MDk= 461 Paginate + search for databases/tables on the homepage simonw 9599 open 0   Datasette 1.0 3268330 4 2019-05-11T18:05:34Z 2020-12-17T22:14:46Z   OWNER  

Split out from #460 - in order to support large numbers of connected databases the homepage needs to be paginated.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/461/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    
443038584 MDU6SXNzdWU0NDMwMzg1ODQ= 465 Decide what to do about /-/inspect simonw 9599 closed 0     4 2019-05-11T21:39:46Z 2019-06-28T16:34:33Z 2019-06-28T16:34:33Z OWNER  

It's not clear to me what this endpoint should do now as a result of #419 - it's still useful to be able to introspect databases for tools like datasette-registry, but since we aren't pre-calculating introspection data any more I need to rethink the approach.

For one thing, this endpoint may need to be paginated. Or maybe it should be split up into separate endpoints for each connected database? Those should probably be paginated too seeing as fivethirtyeight has 400+ tables.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/465/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
443034003 MDU6SXNzdWU0NDMwMzQwMDM= 463 Write release notes for 0.28 simonw 9599 closed 0   0.28 4305096 1 2019-05-11T20:36:56Z 2019-05-19T21:24:44Z 2019-05-19T21:24:20Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/463/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
443023308 MDU6SXNzdWU0NDMwMjMzMDg= 462 Replace most of `.inspect()` (and `datasette inspect`) with table counting simonw 9599 closed 0   0.28 4305096 4 2019-05-11T18:26:06Z 2019-05-16T14:31:05Z 2019-05-16T14:31:05Z OWNER  

This is the last part of #419 - with the move to supporting mutable databases by default, the inspect-data mechanism currently in use no-longer makes much sense.

The one optimization I think it's worth keeping for databases opened in immutable mode is the cached table counts. I think datasette inspect should cut down to only counting the rows in the tables - the other things done by inspect (figuring out columns, foreign key relationships, FTS etc) should all be fast enough that they can be reliably performed at runtime even against large databases.

If performing them at run-time has performance issues, I would rather cache those results internally within Datasette after they are first calculated than continue to support them in the datasette inspect command - to keep things simpler.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/462/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
443034218 MDU6SXNzdWU0NDMwMzQyMTg= 464 Add Glitch to Getting Started docs section simonw 9599 closed 0   0.28 4305096 1 2019-05-11T20:39:39Z 2019-05-16T05:04:35Z 2019-05-16T05:03:46Z OWNER  

Glitch is by far the easiest way to start trying out Datasette. Add a section to https://datasette.readthedocs.io/en/latest/getting_started.html

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/464/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
443020810 MDU6SXNzdWU0NDMwMjA4MTA= 460 Design changes to homepage to support mutable files simonw 9599 closed 0   0.28 4305096 5 2019-05-11T17:58:05Z 2019-05-16T03:34:09Z 2019-05-16T03:24:16Z OWNER  

Needed for #419 - since we can now start up Datasette with a whole bunch of large connected databases that are mutable we can no longer guarantee a quick count of rows across all of the tables.

New proposed homepage tweaks:

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/460/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
443020048 MDU6SXNzdWU0NDMwMjAwNDg= 459 Fix the "datasette now publish ... --alias=x" option simonw 9599 closed 0   0.28 4305096 3 2019-05-11T17:48:40Z 2019-05-11T20:22:08Z 2019-05-11T20:22:08Z OWNER  

Now have deprecated the mechanism we were using for this - running now alias without any parameters - in favour of something new:

https://zeit.co/blog/automatic-aliasing

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/459/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]);