issue_comments

Table actions

5 rows where issue = 702386948 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • simonw · 5 ✖

issue 1

  • .delete_where() does not auto-commit (unlike .insert() or .upsert()) · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
693695177 https://github.com/simonw/sqlite-utils/issues/159#issuecomment-693695177 https://api.github.com/repos/simonw/sqlite-utils/issues/159 MDEyOklzc3VlQ29tbWVudDY5MzY5NTE3Nw== simonw 9599 2020-09-16T22:17:53Z 2020-09-16T22:17:53Z OWNER

@spdkils can you share a minimal code example that exhibits the behavior you're seeing?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 .delete_where() does not auto-commit (unlike .insert() or .upsert()) 702386948  
693694968 https://github.com/simonw/sqlite-utils/issues/159#issuecomment-693694968 https://api.github.com/repos/simonw/sqlite-utils/issues/159 MDEyOklzc3VlQ29tbWVudDY5MzY5NDk2OA== simonw 9599 2020-09-16T22:17:19Z 2020-09-16T22:17:19Z OWNER

That's strange... this test here doesn't manually commit a transaction and passes:

https://github.com/simonw/sqlite-utils/blob/7805d53bcf11199bd1f2b07e05ae90151f9d0eb0/tests/test_delete.py#L17-L23

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 .delete_where() does not auto-commit (unlike .insert() or .upsert()) 702386948  
693694343 https://github.com/simonw/sqlite-utils/issues/159#issuecomment-693694343 https://api.github.com/repos/simonw/sqlite-utils/issues/159 MDEyOklzc3VlQ29tbWVudDY5MzY5NDM0Mw== simonw 9599 2020-09-16T22:15:39Z 2020-09-16T22:15:39Z OWNER

Independent of the transaction changes in #121 I may be able to check self.conn.in_transaction to see if a transaction is active and, if one is NOT active, execute the delete inside of one. https://docs.python.org/3/library/sqlite3.html#sqlite3.Connection.in_transaction

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 .delete_where() does not auto-commit (unlike .insert() or .upsert()) 702386948  
693589321 https://github.com/simonw/sqlite-utils/issues/159#issuecomment-693589321 https://api.github.com/repos/simonw/sqlite-utils/issues/159 MDEyOklzc3VlQ29tbWVudDY5MzU4OTMyMQ== simonw 9599 2020-09-16T18:41:42Z 2020-09-16T18:41:42Z OWNER

Yeah I'm going to class this as a bug - that's definitely confusing.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 .delete_where() does not auto-commit (unlike .insert() or .upsert()) 702386948  
693199049 https://github.com/simonw/sqlite-utils/issues/159#issuecomment-693199049 https://api.github.com/repos/simonw/sqlite-utils/issues/159 MDEyOklzc3VlQ29tbWVudDY5MzE5OTA0OQ== simonw 9599 2020-09-16T06:20:26Z 2020-09-16T06:20:26Z OWNER

See #121 - I need to think harder about how this all interacts with transactions.

You can do this:

python with db.conn: db["mytable"].delete_where() But that should be documented and maybe rethought.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 .delete_where() does not auto-commit (unlike .insert() or .upsert()) 702386948  

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