SQL Explorer aims to make the flow of data between people fast, simple, and confusion-free.

Quickly write and share SQL queries in a simple, usable SQL editor, preview the results in the browser, share links to download CSV files, and keep the information flowing!

Explorer values simplicity, intuitive use, unobtrusiveness, stability, and the principle of least surprise.

Django SQL Explorer is inspired by any number of great query and reporting tools out there.

The original idea came from Stack Exchange's Data Explorer, but also owes credit to similar projects like Redash and Blazer.

django-sql-explorer is MIT licensed, and pull requests are welcome.

A view of a query

Viewing all queries

Quick access to DB schema info

Snapshot query results to S3 & download as csv

• Security

  • Let's not kid ourselves - this tool is all about giving people access to running SQL in production. So if that makes you nervous (and it should) - you've been warned. Explorer makes an effort to not allow terrible things to happen, but be careful! It's recommended you use the EXPLORER_CONNECTION_NAME setting to connect SQL Explorer to a read-only database role.
  • Explorer supports two different permission checks for users of the tool. Users passing the EXPLORER_PERMISSION_CHANGE test can create, edit, delete, and execute queries. Users who do not pass this test but pass the EXPLORER_PERMISSION_VIEW test can only execute queries. Other users cannot access any part of Explorer. Both permission groups are set to is_staff by default and can be overridden in your settings file.
  • Enforces a SQL blacklist so destructive queries don't get executed (delete, drop, alter, update etc). This is not bulletproof and it's recommended that you instead configure a read-only database role, but when not possible the blacklist provides reasonable protection.

• Easy to get started

  • Built on Django's ORM, so works with Postgresql, Mysql, and Sqlite.
  • Small number of dependencies.
  • Just want to get in and write some ad-hoc queries? Go nuts with the Playground area.

• new Snapshots

  • Tick the 'snapshot' box on a query, and Explorer will upload a .csv snapshot of the query results to S3. Configure the snapshot frequency via a celery cron task, e.g. for daily at 1am:

  'explorer.tasks.snapshot_queries': {
      'task': 'explorer.tasks.snapshot_queries',
      'schedule': crontab(hour=1, minute=0)
  }

  • Requires celery, obviously. Also uses djcelery and tinys3. All of these deps are optional and can be installed with pip install -r optional-requirements.txt
  • The checkbox for opting a query into a snapshot is ALL THE WAY on the bottom of the query view (underneath the results table).

• Email query results

  • Click the email icon in the query listing view, enter an email address, and the query results (zipped .csv) will be sent to you asynchronously. Very handy for long-running queries.

• Parameterized Queries

  • Use $$foo$$ in your queries and Explorer will build a UI to fill out parameters. When viewing a query like 'SELECT * FROM table WHERE id=$$id$$', Explorer will generate UI for the 'id' parameter.
  • Parameters are stashed in the URL, so you can share links to parameterized queries with colleagues
  • Use $$paramName:defaultValue$$ to provide default values for the parameters.

• Schema Helper

  • /explorer/schema/ renders a list of your Django apps' table and column names + types that you can refer to while writing queries. Apps can be excluded from this list so users aren't bogged down with tons of irrelevant tables. See settings documentation below for details.
  • This is available quickly as a sidebar helper while composing queries (see screenshot)
  • Quick search for the tables/django models you are looking for. Just start typing!

• Template Columns

  • Let's say you have a query like 'select id, email from user' and you'd like to quickly drill through to the profile page for each user in the result. You can create a "template" column to do just that.
  • Just set up a template column in your settings file:

  EXPLORER_TRANSFORMS = [('user', '<a href="https://yoursite.com/profile/{0}/">{0}</a>')]

  • And change your query to 'SELECT id AS "user", email FROM user'. Explorer will match the "user" column alias to the transform and merge each cell in that column into the template string. Cool!

• Pivot Table

  • Go to the Pivot tab on query results to use the in-browser pivot functionality (provided by Pivottable JS).
  • Hit the link icon on the top right to get a URL to recreate the exact pivot setup to share with colleagues.

• Query Logs

  • Explorer will save a snapshot of every query you execute so you can recover lost ad-hoc queries, and see what you've been querying.
  • This also serves as cheap-and-dirty versioning of Queries, and provides the 'run count' property and average duration in milliseconds, by aggregating the logs.
  • You can also quickly share playground queries by copying the link to the playground's query log record -- look on the top right of the sql editor for the link icon.
  • If Explorer gets a lot of use, the logs can get beefy. explorer.tasks contains the 'truncate_querylogs' task that will remove log entries older than <days> (30 days and older in the example below).

  'explorer.tasks.truncate_querylogs': {
      'task': 'explorer.tasks.truncate_querylogs',
      'schedule': crontab(hour=1, minute=0),
      'kwargs': {'days': 30}
  }

• Power tips

  • On the query listing page, focus gets set to a search box so you can just navigate to /explorer and start typing the name of your query to find it.
  • Quick search also works after hitting "Show Schema" on a query view.
  • Command+Enter and Ctrl+Enter will execute a query when typing in the SQL editor area.
  • Hit the "Format" button to format and clean up your SQL (this is non-validating -- just formatting).
  • Use the Query Logs feature to share one-time queries that aren't worth creating a persistent query for. Just run your SQL in the playground, then navigate to /logs and share the link (e.g. /explorer/play/?querylog_id=2428)
  • Click the 'history' link towards the top-right of a saved query to filter the logs down to changes to just that query.
  • If you need to download a query as something other than csv but don't want to globally change delimiters via settings.EXPLORER_CSV_DELIMETER, you can use /query/download?delim=| to get a pipe (or whatever) delimited file. For a tab-delimited file, use delim=tab. Note that the file extension will remain .csv
  • If a query is taking a long time to run (perhaps timing out) and you want to get in there to optimize it, go to /query/123/?show=0. You'll see the normal query detail page, but the query won't execute.
  • Set env vars for EXPLORER_TOKEN_AUTH_ENABLED=TRUE and EXPLORER_TOKEN=<SOME TOKEN> and you have an instant data API. Just:

  curl --header "X-API-TOKEN: <TOKEN>" https://www.your-site.com/explorer/<QUERY_ID>/stream?format=csv

Requires Python 2.7, 3.4, or 3.5. Requires Django 1.7.1 or higher.

Install with pip from github:

pip install django-sql-explorer

Add to your installed_apps:

INSTALLED_APPS = ( ..., 'explorer', ... )

Add the following to your urls.py (all Explorer URLs are restricted via the EXPLORER_PERMISSION_VIEW and EXPLORER_PERMISSION_CHANGE settings. See Settings section below for further documentation.):

url(r'^explorer/', include('explorer.urls')),

Run migrate to create the tables:

python manage.py migrate

You can now browse to https://yoursite/explorer/ and get exploring! It is highly recommended that you also configure Explorer to use a read-only database connection via the EXPLORER_CONNECTION_NAME setting.

An effort has been made to keep the number of dependencies to a minimum.

Python

• sqlparse is Used for SQL formatting

Python - Optional Dependencies

• Factory Boy is required for tests
• celery is required for the 'email' feature, and for snapshots
• tinys3 is required for snapshots
• xlsxwriter is required for Excel export (csv still works fine without it)

JavaScript

- All all served from CDNJS except for jQuery UI, which uses a custom build, served locally. pivottable.js relies on jQuery UI but for the Sortable method.

Factory Boy is needed if you'd like to run the tests, which can you do easily:

python manage.py test

and with coverage:

coverage run --source='.' manage.py test

then:

coverage report

...99%! Huzzah!

There is also a test_project that you can use to kick the tires. Just creata a new virtualenv, cd into test_project and run start.sh (or walk through the steps yourself) to get a test instance of the app up and running.

Release process is documented here. If there are problems with the release, please help me improve the process so it doesn't happen again!