Releases: simonw/django-sql-dashboard
Releases · simonw/django-sql-dashboard
1.2
1.1
1.0.2
1.0.1
1.0
- Implemented a new column cog menu, with options for sorting, counting distinct items and counting by values. #57
- Fixed bug where columns named after PostgreSQL reserved words (such as
on
orgroup
) produced invalid suggested SELECT queries. #134 - New Docker Compose configuration to support Docker development environments. Thanks, Atul Varma. #128
- Admin change list view now only shows dashboards the user has permission to edit. Thanks, Atul Varma. #130
0.16
- This release includes a small potentially backwards-incompatible change: the
description
field for a saved dashboard is now treated as Markdown and rendered as such when the saved dashboard is displayed. It is very unlikely that this will affect any of your existing dashboards but you should still check before applying the upgrade. Thanks, Atul Varma. #115
0.15.1
0.15
- Configuration instructions for people using
dj-database-url
anddjango-configurations
- thanks, Paolo Melchiorre. #110 - Added a useful SQL pattern to the progress bar widget documentation.
- SQL queries on saved dashboards are now hidden behind a details/summary element. #117
- Documentation now covers the execute_sql permission. #112
0.14
- 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 - Bar charts now preserve the order in which the data is returned by the query. #106
- Example select statements now include explicit columns. #105
- Columns on the dashboard page now respond to media queries, collapsing to a single column on narrow or mobile browser windows. #106
- Fixed hard-coded
/dashboard/
URL, thanks Flávio Juvenal da Silva Junior. #99 - Fixed bug where
?_save-
parameters could be accidentally reflected in the query string. #104 - Explicitly require at least Django 3.0. #101
- Fixed a warning about
AutoField
migrations with Django 3.2. #103 - Fixed a bug where users lacking permissions could end up in an infinite redirect. #30
- Configuration and security documentation now recommends using a read-only database replica as the most robust option. #95
- Added screenshots and demo links for all of the included widgets. #96