issue_comments

Table actions

7 rows where author_association = "OWNER", issue = 1124237013 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • simonw · 7 ✖

issue 1

  • Add SpatiaLite helpers to CLI · 7 ✖

author_association 1

  • OWNER · 7 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1040965672 https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1040965672 https://api.github.com/repos/simonw/sqlite-utils/issues/398 IC_kwDOCGYnMM4-C-Ao simonw 9599 2022-02-16T01:02:29Z 2022-02-16T01:02:29Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add SpatiaLite helpers to CLI 1124237013  
1030732222 https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1030732222 https://api.github.com/repos/simonw/sqlite-utils/issues/398 IC_kwDOCGYnMM49b7m- simonw 9599 2022-02-06T01:42:19Z 2022-02-06T01:42:28Z OWNER

Adding some thoughts to: - #399 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add SpatiaLite helpers to CLI 1124237013  
1030732093 https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1030732093 https://api.github.com/repos/simonw/sqlite-utils/issues/398 IC_kwDOCGYnMM49b7k9 simonw 9599 2022-02-06T01:41:37Z 2022-02-06T01:41:37Z OWNER

Yeah I'd like to avoid adding any geo-dependencies to sqlite-utils if I can avoid it. I'm fine using stuff that's going to be available in SpatiaLite itself (provided it's available as a SQLite module) since then I don't need to add any extra Python dependencies.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add SpatiaLite helpers to CLI 1124237013  
1030534868 https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1030534868 https://api.github.com/repos/simonw/sqlite-utils/issues/398 IC_kwDOCGYnMM49bLbU simonw 9599 2022-02-05T06:03:38Z 2022-02-05T06:03:38Z OWNER

@eyeseast how do you usually insert geometries at the moment?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add SpatiaLite helpers to CLI 1124237013  
1030521533 https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1030521533 https://api.github.com/repos/simonw/sqlite-utils/issues/398 IC_kwDOCGYnMM49bIK9 simonw 9599 2022-02-05T04:25:49Z 2022-02-05T04:25:49Z OWNER

For ingesting geometry data from the command-line maybe GeoJSON would be the best route?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add SpatiaLite helpers to CLI 1124237013  
1030456717 https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1030456717 https://api.github.com/repos/simonw/sqlite-utils/issues/398 IC_kwDOCGYnMM49a4WN simonw 9599 2022-02-05T00:16:42Z 2022-02-05T00:16:42Z OWNER

The one thing worth highlighting in docs is that geometry columns can only be added to existing tables. Trying to add a geometry column to a table that doesn't exist yet might mean you have a schema like {"rowid": int, "geometry": bytes}. Might be worth nudging people to explicitly create a table first, then add geometry columns.

That's a good call. I'm happy for sqlite-utils add-geometry-column to throw an error if the table doesn't exist yet.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add SpatiaLite helpers to CLI 1124237013  
1030454114 https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1030454114 https://api.github.com/repos/simonw/sqlite-utils/issues/398 IC_kwDOCGYnMM49a3ti simonw 9599 2022-02-05T00:14:47Z 2022-02-05T00:14:47Z OWNER

I like these designs a lot. I would suggest sqlite-utils create database.db --init-spatialite there for consistency with the sqlite-utils init-spatialite database.db command.

The other part of this story is how we support actually inserting spatial data from the command-line. I opened an issue about the challenges in doing that for the Python API here - #399 - but we need a good answer for the CLI too.

I don't yet have any good ideas here. The conversions= option in the Python library was designed to cover these kinds of cases but it's pretty clunky and I don't think it's very widely used: https://sqlite-utils.datasette.io/en/stable/python-api.html#converting-column-values-using-sql-functions

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add SpatiaLite helpers to CLI 1124237013  

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])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);