{"html_url": "https://github.com/simonw/datasette/issues/124#issuecomment-347236102", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/124", "id": 347236102, "node_id": "MDEyOklzc3VlQ29tbWVudDM0NzIzNjEwMg==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2017-11-27T16:24:15Z", "updated_at": "2017-11-27T16:24:15Z", "author_association": "OWNER", "body": "I'd really like to get some benchmarks working so I can see the actual impact of this kind of thing.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 275125805, "label": "Option to open readonly but not immutable"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/124#issuecomment-347123991", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/124", "id": 347123991, "node_id": "MDEyOklzc3VlQ29tbWVudDM0NzEyMzk5MQ==", "user": {"value": 50138, "label": "janimo"}, "created_at": "2017-11-27T09:25:15Z", "updated_at": "2017-11-27T09:25:15Z", "author_association": "NONE", "body": "That's the only reference to immutable I saw as well, making me think that there may be no perceivable advantages over simply using mode=ro. Since the database is never or seldom updated the change notifications should not impact performance.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 275125805, "label": "Option to open readonly but not immutable"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/153#issuecomment-347051331", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/153", "id": 347051331, "node_id": "MDEyOklzc3VlQ29tbWVudDM0NzA1MTMzMQ==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2017-11-27T00:23:40Z", "updated_at": "2017-11-27T03:58:49Z", "author_association": "OWNER", "body": "One quick fix could be to add a `extra_css_url` key to the `metadata.json` format (which currently hosts `title`, `license_url` etc) - if populated, we can inject a link to that stylesheet on every page. We could add a few classes in strategic places that include the database and table names to give people styling hooks.\r\n\r\nWhile we're at it, an `extra_js_url` key would let people go really nuts!", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 276842536, "label": "Ability to customize presentation of specific columns in HTML view"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/153#issuecomment-347050235", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/153", "id": 347050235, "node_id": "MDEyOklzc3VlQ29tbWVudDM0NzA1MDIzNQ==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2017-11-27T00:06:24Z", "updated_at": "2017-11-27T00:06:24Z", "author_association": "OWNER", "body": "I've been thinking about 1. a bit - I actually think it would be fine to have a rule that says \"if the contents of the cell starts with `http://` or `https://` and doesn't contain any whitespace, turn that into a link\". If you need the non-linked version that will always be available in the JSON.\r\n\r\nFor the other two... I think #12 may be the way to go here: if you can easily over-ride the `row.html` and `table.html` templates for specific databases you can easily set pre-formatted text or similar for certain values - maybe even with CSS that targets a specific table column.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 276842536, "label": "Ability to customize presentation of specific columns in HTML view"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/124#issuecomment-347049888", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/124", "id": 347049888, "node_id": "MDEyOklzc3VlQ29tbWVudDM0NzA0OTg4OA==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2017-11-27T00:01:08Z", "updated_at": "2017-11-27T00:01:08Z", "author_association": "OWNER", "body": "https://sqlite.org/c3ref/open.html Is the only documentation I've been able to find of the immutable option:\r\n\r\n> **immutable**: The immutable parameter is a boolean query parameter that indicates that the database file is stored on read-only media. When immutable is set, SQLite assumes that the database file cannot be changed, even by a process with higher privilege, and so the database is opened read-only and all locking and change detection is disabled. Caution: Setting the immutable property on a database file that does in fact change can result in incorrect query results and/or SQLITE_CORRUPT errors. ", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 275125805, "label": "Option to open readonly but not immutable"}, "performed_via_github_app": null}