github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/sqlite-utils/issues/114#issuecomment-656363548 | https://api.github.com/repos/simonw/sqlite-utils/issues/114 | 656363548 | MDEyOklzc3VlQ29tbWVudDY1NjM2MzU0OA== | 9599 | 2020-07-09T21:37:28Z | 2020-07-09T21:37:28Z | OWNER | I'm going to add a second method `.transform_table_sql(...)` - which returns the SQL that would have been executed but does NOT execute it. Advanced callers can use this to include their own additional steps in the same transaction - e.g. recreating views or triggers. More importantly it gives me a useful hook for writing some unit tests against the generated SQL. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
621989740 | |
https://github.com/simonw/sqlite-utils/issues/121#issuecomment-655898722 | https://api.github.com/repos/simonw/sqlite-utils/issues/121 | 655898722 | MDEyOklzc3VlQ29tbWVudDY1NTg5ODcyMg== | 79913 | 2020-07-09T04:53:08Z | 2020-07-09T04:53:08Z | CONTRIBUTOR | Yep, I agree that makes more sense for backwards compat and more casual use cases. I think it should be possible for the Database/Queryable methods to DTRT based on seeing if it's within a context-manager-managed transaction. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
652961907 |