The PostgreSQL Cheat Sheet (Part 2)

Introduction to the PostgreSQL cheat sheet

The PostgreSQL offers scaling, storage flexibility, and ease of database management for developers, DBAs, and other technical professionals. Because of PostgreSQL’s ability to offer architecture stability along with an extensive coding capability, the plethora of commands and statements are endless. That’s a good thing. What’s even better is having a handy list of the SQL commands you’re likely to use regularly. Well, some of the most popular ones are featured here in Part 2 of The PostgreSQL Cheat Sheet, so take a few moments to review it now.

Prerequisites to using PostgreSQL SQL commands in psql

• Be sure that the object-relational database management systemPostgreSQL installed on your OS.

• At the command line psql, check the PostgreSQL version with the command psql -V.

• You’ll also need PostgreSQL database accessibility to try out the samples shown in this PostgreSQL cheat sheet.

NOTE: Here are some useful tips regarding commands. When writing code in psql, always end your SQL statement with a semicolon (;). If you don’t and push Return, your code will extend to the next line of code without breaking at the place where you wanted it to end.

Another tip for writing SQL statements is to remember to enclose your strings in PostgreSQL with singular quotes, not doubles. This one is correct: 'string here' for example. A syntax error will happen if you use doubles.

Finally, to quickly get away from a long results list or a command you started or completed, push CTRL+C.

Accessing PostgreSQL using the ‘psql’ command line interface

• From your server on your localhost, connect to your database in PostgreSQL with the command psql.

• Alternatively to the above command, input your username, host, and then database name to make a Postgres database connection.

NOTE: See the flags in the above code.

• Your username in Postgres comes after the flag -U
• The IP address or host domain goes after the flag -h
• The database PostgreSQL name is inputted after the flag -d

PostgreSQL cheat sheet of useful SQL queries and commands

This PostgreSQL cheat sheet contains some of the most frequently-used commands to perform basic computing software programming functions so that you can code with efficiency.

Use ‘SELECT’ to get a Postgres table’s column names

• Obtain the names of a table’s columns with the information_schema command:

• You can also access the names of a public table’s column with the table_schema command:

PostgreSQL cheat sheet commands for modifying tables

• Use the INSERT INTO statement to add a value to a table:

NOTE: The above command adds two columns and two values. See (col1, col2) and (value1, value2) in the SQL statement. Place a comma after each indicated column or value within the parenthesis when you have more than one to add to a table.

• Use the INSERT INTO and SELECT statement to add a table’s column data to a different table:

• Save table updates with the UPDATE statement:

• Use the UPDATE statement for condition matching in a table:

• Use the DELETE FROM statement to remove all records from a table in Postgres:

NOTE: An option to remove all records from a table in Postgres is to use the command TRUNCATE followed by naming the table you want to delete.

• Use the DELETE FROM statement to remove data pertaining to a condition:

PostgreSQL cheat sheet for managing databases

• Make a database with the CREATE DATABASE statement:

NOTE: A database may already exist, so to avoid raising an exception, use the IF NOT EXISTS clause after the CREATE DATABASE statement.

• Use DROP DATABASE to delete a database forever:

NOTE: You won’t get an error message prompt if you add the IF NOT EXISTS clause.

Use the a PostgreSQL ‘SELECT’ statement to query data

Query data in a table with these various SELECT statement command.

• Add the wildcard asterisk * symbol to have every record in a PostgreSQL table return in the results page.

• Indicate which columns to query:

• Query a filtered table:

• Include the clause WHERE to specify the columns you want to query:

• Perform a column query and give the column an alias with this statement:

Here are some commands to query in PostgreSQL using operators.

• Use the operator LIKE to query a character string pattern match:

To query a set of operations in PostgreSQL:

Using the LIKE operator:

• Use the operator BETWEEN to query a table range:

• Use the operator IN to add more than one condition or value to your WHERE clause in your statement:

• Use the operator UNION to merge at least two SELECT statement results sets.

• Use the operator EXCEPT to put together two SELECT statements that will only return rows that are not in the second statement.

• Use the operator INTERSECT to have the results set to reflect every record picked by at least two statements. If a record fails to match each query, it won’t appear in the results set:

• Use the clause LIMIT to return a limited amount of rows. In the statement below, OFFSET rows are skipped:

Here are a few SQL statements for querying multiple tables.

• Make a multiple Postgres table query with the INNER JOIN statement:

• Make a multiple Postgres table query with the LEFT JOIN statement:

• Make a multiple Postgres table query with the FULL OUTER JOIN statement:

• Make a multiple Postgres table query with the CROSSJOIN statement:

• Make a multiple Postgres table query with the NATURAL JOIN statement:

Here are a few common SELECT statements for displaying table rows.

• Use the wildcard (*) to show all table rows:

• Use the ORDER BY clause to sort the order of table rows in the results:

• To group table data, use the clause GROUP BY:

• Use both clauses HAVING and GROUP BY to specify the criteria for grouping the data results:

Conclusion on the PostgreSQL cheat sheet

A helpful PostgreSQL cheat sheet is meant to help you reduce the time you spend on your daily coding projects. Make it an accessible reference of common SQL statements and other commands are at your fingertips. This way, you won’t have to wonder if the syntax is off the mark. The most beneficial result is that you’ll likely cut down on unnecessarily raised exceptions every day.