Tags: earlbread/django-sql-explorer
Tags
0.9.1
=====
2/1/2016
- Major changes
- Dropped support for Django 1.6, added support for Django 1.9. See .travis.yml for test matrix.
- Dropped charted.js & visualization because it didn't work well.
- Client-side pivot tables with pivot.js. This is ridiculously cool!
- Minor (but awesome!) changes
- Cmd-/ to comment/uncomment a block of SQL
- Quick 'shortcut' links to the corresponding querylog to more quickly share results. Look at the top-right of the editor. Also works for playground!
- Prompt for unsaved changes before navigating away
- Support for default parameter values via $$paramName:defaultValue$$
- Optional Celery task for truncating query logs as entries build up
- Display historical average query runtime
- Increased default number of rows from 100 to 1000
- Increased SQL editor size (5 additional visible lines)
- CSS cleanup and streamlining (making better use of foundation)
- Various bugfixes (blacklist not enforced on playground being the big one)
- Upgraded front-end libraries
- Hide Celery-based features if tasks not enabled.
- Added search functionality to schema view and explorer view (using … …list.js). - Python 2.6 compatibility. - Basic charts via charted (from Medium via charted.co). - SQL formatting function. - Token authentication to retrieve csv version of queries. - Fixed south_migrations packaging issue. - Refactored front-end and pulled CSS and JS into dedicated files.
0.6.0
=====
11/5/2014
- Introduced Django 1.7 migrations. See readme.rst for info on how to run South migrations if you are not on Django 1.7 yet.
- Upgraded front-end libraries to latest versions.
- Added ability to grant selected users view permissions on selected queries via the EXPLORER_USER_QUERY_VIEWS parameter
- Example usage: EXPLORER_USER_QUERY_VIEWS = {1: [3,4], 2:[3]}
- This would grant user with PK 1 read-only access to query with PK=3 and PK=4 and user 2 access to query 3.
- Bugfixes
- Navigating to an explorer URL without the trailing slash now redirects to the intended page (e.g. /logs -> /logs/)
- Downloading a .csv and subsequently re-executing a query via a keyboard shortcut (cmd+enter) would re-submit the form and re-download the .csv. It now correctly just refreshes the query.
- Django 1.7 compatibility fix
- Query logs! Accessible via explorer/logs/. You can look at previous… …ly executed queries (so you don't, for instance, lose that playground query you were working, or have to worry about mucking up a recorded query). It's quite usable now, and could be used for versioning and reverts in the future. Itan be accessed at explorer/logs/ - Actually captures the creator of the query via a ForeignKey relation, instead of just using a Char field. - Re-introduced type information in the schema helpers. - Proper relative URL handling after downloading a query as CSV. - Users with view permissions can use query parameters. There is potential for SQL injection here. I think about the permissions as being about preventing users from borking up queries, not preventing them from viewing data. You've been warned. - Refactored params handling for extra safety in multi-threaded environments.
PreviousNext