TopAnswers
or
Meta Question: A fiddle for TopAnswers Databases
, by Jack Douglas CC0 1.0
[db<>fiddle](https://dbfiddle.uk) was designed with markdown-based Q&A in mind, so it seems sensible to use a post here for comments/suggestions/bug reports. Please feel free to comment in the chat room attached to this post. **Please post concrete feature requests and bug reports as answers below.** Please also post any feature requests and bug reports about db<>fiddle integration with TopAnswers. The current list of supported databases is: * SQL Server 2012, 2014, 2016, 2017, 2017 Linux, 2019 and 2019 Linux RC1 * Postgres 8.4, 9.4, 9.5, 9.6, 10, 11 and 12 * Oracle 11.2 and 18 * MySQL 5.6, 5.7 and 8.0 * MariaDB 10.2, 10.3 and 10.4 * SQLite 3.8, 3.16 and 3.27 (but 3.16 is currently offline for [security reasons](https://security-tracker.debian.org/tracker/CVE-2018-20346)) * Db2 Developer-C 11.1 (with lots of thanks to [@mustaccio](https://dba.meta.stackexchange.com/users/23721/mustaccio)) * Firebird 3.0 Here's an example (the image links to the fiddle): [![SQL Server 2019 'help'](/image?hash=407870c3b82d22484cb884d64c05e7a70ca3f3e97cd776b4f82cf701a55e56a3) ](https://dbfiddle.uk/?rdbms=sqlserver_2019&fiddle=9bcd60e2bcd7966fc3be475addab8eb2) and here's a really interesting one just for fun: [![Naughts and Crosses](/image?hash=91efa2c2370e503e4158d295924693af7ce4f9eb25d8435126c2fcbb87e690fd)](https://dbfiddle.uk/?rdbms=postgres_11&fiddle=71940aadda50f55bfede87606cd1dc2c) finally, just because we can, here is the same fiddle integrated into this post. You can edit it and run it live right here: <>https://dbfiddle.uk/?rdbms=postgres_11&fiddle=71940aadda50f55bfede87606cd1dc2c
score: 3
Top Answer
CC BY-SA 4.0 by PeterVandivier
Currently it looks like editing and/or running the fiddle from the embed doesn't change the post. This is obviously good design, but I suggest adding an `Update this post` button or something similar alongside the embedding. This would make it clear to the user that the underlying post may need to be modified if they want it to persist the changes they have just typed Some related thoughts: * Button could hotlink to the `/edit` analogue with the commit message pre-populated à la "_updated fiddle from `abc` to `def`_" * Perhaps the button only appears on-edit or on-run when a new fiddle hash is generated? * Does it make sense to track a fiddle's "lineage" & possibly expose it to users to "_go back to that one edit I forgot what I did on but I know what the results looked like_" * Is there a not-gross way to expose the diff of either the post batch or the last-run batch to the active editor in the embed?
score: 1
transcript