You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've spent very little time on SQL queries so far.
The main idea was to make 4 switches with different types of queries, including bad queries that run slow or even extremely slow, to find problems in monitoring or to show the impact of bad queries on performance.
Initially when I started the project, I wanted to compare MySQL, PG, MongoDB with the same data and queries. But then it turned into something more.
I plan to improve both Dataset and SQL switch queries in the future.
I'll tell you right away, Switch 1 and Switch 2 will be for good queries, Switch 3 and Switch 4 for bad, slow or no index.
I can also make some Switch to delete the index on power on and create it on power off.
There is a lot of room and flexibility for improvement.
You can add new tables and columns.
As a dataset I use GitHub data from API, right now only Repos and Pulls, but in the future I will add other data like Issues, Comments, Tags or something like that.
By the way, you can change the Dataset type to GitHub, put as GitHub_ORG your organization, for demo_app_dataset service. Then the app will import your organization's repository data into the dataset. But you also need to set GITHUB_API for using it
For the following query (PostgresSwitch4):
Why is it cast from text to timestamp and then back to text?
The problem is that this function is not immutable and cannot be indexed.
With the followingquery, an index
on github.pulls ((data->>'created_at') asc)
could be usedThe text was updated successfully, but these errors were encountered: