Why Use WHERE 1=2 in SQL
Some time ago I wrote short blog post on why use WHERE 1=1 in SQL. This time it’s why use WHERE 1=2, but really this can be WHERE 1=9 or anything that isn’t a 1, we just want the false statement.
Redshift JDBC Driver Download
A handy post to note down the JDBC client driver download. I’m frequently in need of this myself. You can download the JDBC driver from the AWS Docs and then gain your cluster endpoint address from the main Redshift dashboard window Instead of doing the above, you navigate to the Configure tab in the Redshift console and download the JDBC driver &
List all Schemas/Tables/Columns in Redshift & Postgres
This is a post containing a query that’ll bring back all schemas, tables, and columns in Redshift or Postgres databases. I’m combining the Redshift and Postgres database blog categories here…
Create a Superuser in RedShift
Superusers in RedShift hold the permissions to perform any action in the cluster, the same access as ‘master’ or whatever you named the superuser during creation.
Create a Test AWS RedShift Cluster
Here’s a simple guide on creating a new AWS RedShift Cluster within a personal AWS test environment. Warning, if you’re testing this AWS Service you have to be rigorous with managing the cluster for billing reasons.
Why use WHERE 1=1 in SQL Queries
A common SQL question is, why does anyone use WHERE 1=1 in their queries? And what does it do? The condition means WHERE TRUE, so it’s just bringing back the same query result as it would without.
