Share on facebook
Share on linkedin
Share on twitter
Share on reddit

What’s new in superQuery: July 2020

After a brief hiatus, we’re back to our regularly scheduled programming of monthly superQuery product updates.

Here are the most important updates since the beginning of 2020!

New Git functionalities

Users who’ve connected superQuery to their Github repositories will be happy with this news! 

We’re introducing three new Git-related features to enhance our integration with Github:

Git Ignore: Now in your Query Tab Settings you can toggle on Git Ignore so that your queries won’t be committed to your repo. Up until now, when you had the Github integration set up, all executed queries were automatically committed. 

Manual Commit: When Git Ignore is toggled on, override this with a Manual Commit.

Commit Messages: Meaningful navigation of your query version history is important as the SQL changes over time. With Commit Messages you’ll be able to give more context around the edits you make.

 

Don’t use Github? Let us know which repositories we should support next.

 

Git Ignore and Auto-commit in superQuery
Toggle Git Ignore and Auto Commit in Query Tab Settings
Git Manual Commit and Commit Messages in superQuery
Manual Commit + Commit Messages

Limitless data points in Charts

Chart visualizations now support an unlimited amount of rows. Moreover, you can also zoom into a sub-section of the results to take a closer look.

Local History (AKA Git Diff) for Queries

Those familiar with Git commands and version control will know “Git Diff“, which lets you compare the differences between two commits

With Local History in superQuery, you now have Git Diff functionality for your queries. This means you can compare the SQL between two versions of a query to better understand how it evolved.**

To access Local History, go to your Query Execution Details and click on the Local History icon in the lower-right corner.

**You can only compare two queries that were executed in the same tab.

Local History for Queries in superQuery
How to access your Local History
View SQL of old results
Diff between two versions of a query

Set default billing projects

Teams can now define a default billing project to be used across your team. This can be overridden when you specify a billing project in your Query Tab Settings. 

Perfect for teams on a flat-rate plan with BigQuery.

To do so, go to Settings > System Preferences and select a project from the “Default Billing Project” dropdown.

Default Billing Project

One-click Copy to Clipboard

Once you run a query, you’ll be able to copy up to the first 16,000 results to clipboard in just one click. 

Download results 4-5x faster

As some users know, with superQuery you can download up to 6,000,000 rows to CSV and Sheets (cell count limitations apply) without having to save results as a table first.

Those large downloads will now complete much faster thanks to Google Cloud’s recently-made-available Storage API.

View SQL of old query results

With superQuery, you can execute a query multiple times, with each result getting its own result tab. This saved tons of time for BigQuery users frustrated with having to re-run queries to get old results.

With our latest update, you can also view the SQL of older results right inside of your Query Execution Details. Just make sure the correct result tab is selected.

Two-character search for projects

You now only need to enter a minimum of two characters in the Projects Search box for search results to start appearing. Prior to this update, you needed at least three characters entered.

Share Query Tabs

Teams looking to share individual tabs without giving access to their entire board can now do so  — without having to duplicate the tab.

This way, there is a universal source of truth and you have more control over access to your queries.

Connect DynamoDB to superQuery

While superQuery was originally built for Google BigQuery, we’ve started adding support for other databases — beginning with Amazon DynamoDB. Now you can use full-featured SQL to query DynamoDB — unheard of for a NoSQL database.

In the future, you’ll be able to do cross-database JOINs in superQuery with these connections, without performing any ETL!

Don’t use DynamoDB? Vote for the next database connection superQuery should support.

New superQuery Pricing Plan

Following our recent acquisition by DoiT International earlier this year, we released a brand new plan that lets you and your team enjoy unlimited usage of superQuery — at no additional cost.

Beyond just optimizing BigQuery, this plan will also help your team optimize its entire cloud deployment.

Learn more about the new plan here.

 

What's next for superQuery?

Is there something you feel that we should be focusing on next?

Let the superQuery team know what you’d like us to focus on next HERE.

  • © 2019 superQuery. All rights reserved.