issue_comments

Table actions

5 rows where issue = 1383646615 and "updated_at" is on date 2022-09-26 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Ability to merge databases and tables · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1258712931 https://github.com/simonw/sqlite-utils/issues/491#issuecomment-1258712931 https://api.github.com/repos/simonw/sqlite-utils/issues/491 IC_kwDOCGYnMM5LBm9j eyeseast 25778 2022-09-26T22:31:58Z 2022-09-26T22:31:58Z CONTRIBUTOR

Right. The backup command will copy tables completely, but in the case of conflicting table names, the destination gets overwritten silently. That might not be what you want here. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to merge databases and tables 1383646615  
1258697384 https://github.com/simonw/sqlite-utils/issues/491#issuecomment-1258697384 https://api.github.com/repos/simonw/sqlite-utils/issues/491 IC_kwDOCGYnMM5LBjKo simonw 9599 2022-09-26T22:12:45Z 2022-09-26T22:12:45Z OWNER

That feels like a slightly different command to me - maybe sqlite-utils backup data.db data-backup.db? It doesn't have any of the mechanics for merging tables together. Could be a useful feature separately though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to merge databases and tables 1383646615  
1258508215 https://github.com/simonw/sqlite-utils/issues/491#issuecomment-1258508215 https://api.github.com/repos/simonw/sqlite-utils/issues/491 IC_kwDOCGYnMM5LA0-3 eyeseast 25778 2022-09-26T19:22:14Z 2022-09-26T19:22:14Z CONTRIBUTOR

This might be fairly straightforward using SQLite's backup utility: https://docs.python.org/3/library/sqlite3.html#sqlite3.Connection.backup

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to merge databases and tables 1383646615  
1258450447 https://github.com/simonw/sqlite-utils/issues/491#issuecomment-1258450447 https://api.github.com/repos/simonw/sqlite-utils/issues/491 IC_kwDOCGYnMM5LAm4P simonw 9599 2022-09-26T18:36:23Z 2022-09-26T18:36:23Z OWNER

This is also the kind of feature that would need to express itself in both the Python library and the CLI utility.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to merge databases and tables 1383646615  
1258449887 https://github.com/simonw/sqlite-utils/issues/491#issuecomment-1258449887 https://api.github.com/repos/simonw/sqlite-utils/issues/491 IC_kwDOCGYnMM5LAmvf simonw 9599 2022-09-26T18:35:50Z 2022-09-26T18:35:50Z OWNER

This is a really interesting idea.

I'm nervous about needing to set the rules for how duplicate tables should be merged though. This feels like a complex topic - one where there isn't necessarily an obviously "correct" way of doing it, but where different problems that people are solving might need different merging approaches.

Likewise, merging isn't just a database-to-database thing at that point - I could see a need for merging two tables using similar rules to those used for merging two databases.

So I think I'd want to have some good concrete use-cases in mind before trying to design how something like this should work. Will leave this thread open for people to drop those in!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to merge databases and tables 1383646615  

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