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/datasette/issues/296#issuecomment-506801644 | https://api.github.com/repos/simonw/datasette/issues/296 | 506801644 | MDEyOklzc3VlQ29tbWVudDUwNjgwMTY0NA== | 9599 | 2019-06-28T16:46:34Z | 2019-06-28T16:46:34Z | OWNER | The first of these will be built in #531 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327395270 | |
https://github.com/simonw/datasette/issues/294#issuecomment-506801311 | https://api.github.com/repos/simonw/datasette/issues/294 | 506801311 | MDEyOklzc3VlQ29tbWVudDUwNjgwMTMxMQ== | 9599 | 2019-06-28T16:45:28Z | 2019-06-28T16:45:28Z | OWNER | This can happen as part of #531 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327365110 | |
https://github.com/simonw/datasette/issues/465#issuecomment-506797736 | https://api.github.com/repos/simonw/datasette/issues/465 | 506797736 | MDEyOklzc3VlQ29tbWVudDUwNjc5NzczNg== | 9599 | 2019-06-28T16:34:33Z | 2019-06-28T16:34:33Z | OWNER | I'm closing this because #531 counts as a decision. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
443038584 | |
https://github.com/simonw/datasette/issues/465#issuecomment-506797086 | https://api.github.com/repos/simonw/datasette/issues/465 | 506797086 | MDEyOklzc3VlQ29tbWVudDUwNjc5NzA4Ng== | 9599 | 2019-06-28T16:32:33Z | 2019-06-28T16:32:33Z | OWNER | Next step: - [ ] build `/database/-/inspect` which shows tables, columns, column types and foreign keys It won't show table counts. Or maybe it will include them optionally but only for `-I` databases, in a special area of the JSON reserved for immutable-only inspect details. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
443038584 | |
https://github.com/simonw/sqlite-utils/pull/32#issuecomment-506784912 | https://api.github.com/repos/simonw/sqlite-utils/issues/32 | 506784912 | MDEyOklzc3VlQ29tbWVudDUwNjc4NDkxMg== | 9599 | 2019-06-28T15:55:13Z | 2019-06-28T15:55:13Z | OWNER | Documentation, to be added as a subsection of https://sqlite-utils.readthedocs.io/en/latest/python-api.html#adding-foreign-key-constraints ### Adding multiple foreign key constraints at once The final step in adding a new foreign key to a SQLite database is to run VACUUM, to ensure the new foreign key is available in future introspection queries. VACUUM against a large (multi-GB) database can take several minutes or longer. If you are adding multiple foreign keys using table.add_foreign_key(...) these can quickly add up. Instead, you can use db.add_foreign_keys(...) to add multiple foreign keys within a single transaction. This method takes a list of four-tuples, each one specifying a table, column, other_table and other_column. Here's an example adding two foreign keys at once: db.add_foreign_keys([ ("dogs", "breed_id", "breeds", "id"), ("dogs", "home_town_id", "towns", "id") ]) | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
462094937 |