Django-sql-dashboard

- Fixed 500 error caused when markdown widget attempted to render a null value. [124](https://github.com/simonw/django-sql-dashboard/issues/124)

- Configuration instructions for people using `dj-database-url` and `django-configurations` - thanks, Paolo Melchiorre. [110](https://github.com/simonw/django-sql-dashboard/issues/110)
- Added a useful SQL pattern to the [progress bar widget documentation](https://django-sql-dashboard.datasette.io/en/latest/widgets.html#progress-bar-total-count-completed-count).
- SQL queries on saved dashboards are now hidden behind a details/summary element. [117](https://github.com/simonw/django-sql-dashboard/issues/117)
- Documentation now [covers the execute_sql permission](https://django-sql-dashboard.datasette.io/en/latest/setup.html#django-permissions). [112](https://github.com/simonw/django-sql-dashboard/issues/112)

- Fixed a security and permissions flaw, where users without the `execute_sql` permission could still run custom queries by editing saved dashboards using the Django admin interface. [94](https://github.com/simonw/django-sql-dashboard/issues/94)
- Bar charts now preserve the order in which the data is returned by the query. [106](https://github.com/simonw/django-sql-dashboard/issues/106)
- Example select statements now include explicit columns. [105](https://github.com/simonw/django-sql-dashboard/issues/105)
- Columns on the dashboard page now respond to media queries, collapsing to a single column on narrow or mobile browser windows. [106](https://github.com/simonw/django-sql-dashboard/issues/106)
- Fixed hard-coded `/dashboard/` URL, thanks Flávio Juvenal da Silva Junior. [99](https://github.com/simonw/django-sql-dashboard/issues/99)
- Fixed bug where `?_save-` parameters could be accidentally reflected in the query string. [104](https://github.com/simonw/django-sql-dashboard/issues/104)
- Explicitly require at least Django 3.0. [101](https://github.com/simonw/django-sql-dashboard/issues/101)
- Fixed a warning about `AutoField` migrations with Django 3.2. [103](https://github.com/simonw/django-sql-dashboard/issues/103)
- Fixed a bug where users lacking permissions could end up in an infinite redirect. [30](https://github.com/simonw/django-sql-dashboard/issues/30)
- Configuration and security documentation now recommends using a read-only database replica as the most robust option. [95](https://github.com/simonw/django-sql-dashboard/issues/95)
- Added screenshots and demo links for all of the included [widgets](https://django-sql-dashboard.datasette.io/en/latest/widgets.html). [#96](https://github.com/simonw/django-sql-dashboard/issues/96)

- New word cloud widget displayed when queries return `wordcount_word` and `wordcount_count` columns. [91](https://github.com/simonw/django-sql-dashboard/issues/91)
- All pages are now served with `cache-control: private` header if the user is logged in. [92](https://github.com/simonw/django-sql-dashboard/issues/92)
- Much improved README, including a detailed list of features. [40](https://github.com/simonw/django-sql-dashboard/issues/40)

- Fixed bug where saved dashboards relating to groups could be displayed multiple times. [90](https://github.com/simonw/django-sql-dashboard/issues/90)
- Removed duplicate "Run queries" button. [89](https://github.com/simonw/django-sql-dashboard/issues/89)
- HTML page titles now include named parameter values, if available. [88](https://github.com/simonw/django-sql-dashboard/issues/88)

- Documentation is now hosted at https://django-sql-dashboard.datasette.io/ [#86](https://github.com/simonw/django-sql-dashboard/issues/86)
- Dashboard index link is no longer shown on saved dashboards to to users without permission to view it. [87](https://github.com/simonw/django-sql-dashboard/issues/87)