In PostgreSQL, the round() function is used for rounding a number.
The function can work in one of two ways, depending on how you use it. You can make it round the number to the nearest integer, or to a specified number of decimal places.
This is determined by the number of arguments you pass to the function when you call it.
In Postgres, to_char() is a data type formatting function that converts its first argument to a string.
The format of the string is determined by the second argument.
The to_char() function can be used to do the following conversions:
In SQLite, iif() is a conditional function that returns the second or third argument based on the evaluation of the first argument.
It’s logically equivalent to CASE WHEN X THEN Y ELSE Z END.
iif() is an abbreviation for Immediate IF.
The iif() function was introduced in SQLite 3.32.0, which was released on 22 May 2020.
Some database management systems (DBMSs) include a feature called generated columns.
Also known as “computed columns”, generated columns are similar to a normal column, except that a generated column’s value is derived from an expression that computes values from other columns.
In other words, a generated column’s value is computed from other columns.
SQLite has the ON CONFLICT clause that allows you to specify how to handle constraint conflicts. It applies to UNIQUE, NOT NULL, CHECK, and PRIMARY KEY constraints (but not FOREIGN KEY constraints).
There are five possible options you can use with this clause:
ABORTFAILIGNOREREPLACEROLLBACKThis article provides examples and an explanation of each of these options.
The ON CONFLICT clause is used in CREATE TABLE statements, but it can also be used when inserting or updating data by replacing ON CONFLICT with OR.
In database terms, a CHECK constraint is a type of constraint that checks data before it enters the database.
CHECK constraints help maintain data integrity, because they prevent invalid data entering the database.
In SQLite, an AUTOINCREMENT column is one that uses an automatically incremented value for each row that’s inserted into the table.
There are a couple of ways you can create an AUTOINCREMENT column:
INTEGER PRIMARY KEY. AUTOINCREMENT keyword. One downside of this method is that it uses extra CPU, memory, disk space, and disk I/O overhead.Both methods cause the column to use an incrementing value each time a new row is inserted with NULL in that column.
However, there are some subtle differences between how each method works.
In SQL Server, a temporary table is a certain kind of table that exists until goes out of scope (unless it’s explicitly dropped).
This is different to a regular (persistent) table, where the regular table exists permanently in your database until you explicitly drop it.