{"html_url": "https://github.com/simonw/sqlite-utils/issues/114#issuecomment-656363548", "issue_url": "https://api.github.com/repos/simonw/sqlite-utils/issues/114", "id": 656363548, "node_id": "MDEyOklzc3VlQ29tbWVudDY1NjM2MzU0OA==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2020-07-09T21:37:28Z", "updated_at": "2020-07-09T21:37:28Z", "author_association": "OWNER", "body": "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.\r\n\r\nAdvanced callers can use this to include their own additional steps in the same transaction - e.g. recreating views or triggers.\r\n\r\nMore importantly it gives me a useful hook for writing some unit tests against the generated SQL.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 621989740, "label": "table.transform() method for advanced alter table"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/sqlite-utils/issues/121#issuecomment-655898722", "issue_url": "https://api.github.com/repos/simonw/sqlite-utils/issues/121", "id": 655898722, "node_id": "MDEyOklzc3VlQ29tbWVudDY1NTg5ODcyMg==", "user": {"value": 79913, "label": "tsibley"}, "created_at": "2020-07-09T04:53:08Z", "updated_at": "2020-07-09T04:53:08Z", "author_association": "CONTRIBUTOR", "body": "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.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 652961907, "label": "Improved (and better documented) support for transactions"}, "performed_via_github_app": null}