If you’re using one of SQLite’s tabular output modes, you might find yourself battling with long lines of text that result in all subsequent columns being pushed out far to the right. This can cause you to have to keep scrolling sideways as you peruse the data.
Fortunately, there’s an easy fix.
MySQL and MariaDB have a SHOW TABLES statement, which outputs a list of tables and views in a database. PostgreSQL doesn’t have a SHOW TABLES statement, but it does have a command that produces a similar result.
In Postgres, you can use the \dt command to show a list of tables. This is a psql command (psql is the interactive terminal for PostgreSQL).
It’s possible to output query results as a JSON document when using the SQLite command line interface.
We can do this with the json output mode.
We can also use SQLite functions like json_object() and/or json_array() to return query results as a JSON document.
SQLite has a number of tabular output modes. One of these is called table mode.
Below is an example of using table mode to output SQLite’s query results as a table.
In PostgreSQL, we can use the + operator to add one or more weeks to a date. We have a few options when it comes to specifying the actual number of weeks.
The SQLite command line interface provides us with several options for outputting our results in tabular format.
These can be set using the .mode command. You simply type .mode followed by the desired output format.
Below are examples of the various tabular modes available in SQLite.
The following examples return only those rows that don’t contain any numeric digits in a given column in Oracle Database.
The unix timestamp is the number of seconds since 1970-01-01 00:00:00 UTC. SQLite provides us with a couple of ways to get the unix timestamp.
When using PostgreSQL’s INTERSECT operator, if you encounter an error that reads “ERROR: each INTERSECT query must have the same number of columns“, it’s because there’s a mismatch in the number of columns returned by the queries on either side of the INTERSECT operator.
The way to fix this is to ensure that both SELECT statements return the same number of columns.
Here are examples of removing duplicate rows from a table in MariaDB when those rows have a primary key or unique identifier column.
The examples delete duplicate rows but keep one. So in the case of two identical rows, it deletes one of them and keeps the other.