Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
9.2. Comparison Functions and Operators
Prev UpChapter 9. Functions and OperatorsHome Next

9.2. Comparison Functions and Operators

The usual comparison operators are available, as shown inTable 9.1.

Table 9.1. Comparison Operators

OperatorDescription
<less than
>greater than
<=less than or equal to
>=greater than or equal to
=equal
<> or!=not equal

Note

The!= operator is converted to<> in the parser stage. It is not possible to implement!= and<> operators that do different things.

Comparison operators are available for all relevant data types. All comparison operators are binary operators that return values of typeboolean; expressions like1 < 2 < 3 are not valid (because there is no< operator to compare a Boolean value with3).

There are also some comparison predicates, as shown inTable 9.2. These behave much like operators, but have special syntax mandated by the SQL standard.

Table 9.2. Comparison Predicates

PredicateDescription
aBETWEENxANDybetween
aNOT BETWEENxANDynot between
aBETWEEN SYMMETRICxANDybetween, after sorting the comparison values
aNOT BETWEEN SYMMETRICxANDynot between, after sorting the comparison values
aIS DISTINCT FROMbnot equal, treating null like an ordinary value
aIS NOT DISTINCT FROMbequal, treating null like an ordinary value
expressionIS NULLis null
expressionIS NOT NULLis not null
expressionISNULLis null (nonstandard syntax)
expressionNOTNULLis not null (nonstandard syntax)
boolean_expressionIS TRUEis true
boolean_expressionIS NOT TRUEis false or unknown
boolean_expressionIS FALSEis false
boolean_expressionIS NOT FALSEis true or unknown
boolean_expressionIS UNKNOWNis unknown
boolean_expressionIS NOT UNKNOWNis true or false

TheBETWEEN predicate simplifies range tests:

a BETWEENx ANDy

is equivalent to

a >=x ANDa <=y

Notice thatBETWEEN treats the endpoint values as included in the range.NOT BETWEEN does the opposite comparison:

a NOT BETWEENx ANDy

is equivalent to

a <x ORa >y

BETWEEN SYMMETRIC is likeBETWEEN except there is no requirement that the argument to the left ofAND be less than or equal to the argument on the right. If it is not, those two arguments are automatically swapped, so that a nonempty range is always implied.

Ordinary comparison operators yield null (signifyingunknown), not true or false, when either input is null. For example,7 = NULL yields null, as does7 <> NULL. When this behavior is not suitable, use theIS [ NOT] DISTINCT FROM predicates:

a IS DISTINCT FROMba IS NOT DISTINCT FROMb

For non-null inputs,IS DISTINCT FROM is the same as the<> operator. However, if both inputs are null it returns false, and if only one input is null it returns true. Similarly,IS NOT DISTINCT FROM is identical to= for non-null inputs, but it returns true when both inputs are null, and false when only one input is null. Thus, these predicates effectively act as though null were a normal data value, rather thanunknown.

To check whether a value is or is not null, use the predicates:

expression IS NULLexpression IS NOT NULL

or the equivalent, but nonstandard, predicates:

expression ISNULLexpression NOTNULL

Donot writeexpression = NULL becauseNULL is notequal toNULL. (The null value represents an unknown value, and it is not known whether two unknown values are equal.)

Tip

Some applications might expect thatexpression = NULL returns true ifexpression evaluates to the null value. It is highly recommended that these applications be modified to comply with the SQL standard. However, if that cannot be done thetransform_null_equals configuration variable is available. If it is enabled,PostgreSQL will convertx = NULL clauses tox IS NULL.

If theexpression is row-valued, thenIS NULL is true when the row expression itself is null or when all the row's fields are null, whileIS NOT NULL is true when the row expression itself is non-null and all the row's fields are non-null. Because of this behavior,IS NULL andIS NOT NULL do not always return inverse results for row-valued expressions; in particular, a row-valued expression that contains both null and non-null fields will return false for both tests. In some cases, it may be preferable to writerowIS DISTINCT FROM NULL orrowIS NOT DISTINCT FROM NULL, which will simply check whether the overall row value is null without any additional tests on the row fields.

Boolean values can also be tested using the predicates

boolean_expression IS TRUEboolean_expression IS NOT TRUEboolean_expression IS FALSEboolean_expression IS NOT FALSEboolean_expression IS UNKNOWNboolean_expression IS NOT UNKNOWN

These will always return true or false, never a null value, even when the operand is null. A null input is treated as the logical valueunknown. Notice thatIS UNKNOWN andIS NOT UNKNOWN are effectively the same asIS NULL andIS NOT NULL, respectively, except that the input expression must be of Boolean type.

Some comparison-related functions are also available, as shown inTable 9.3.

Table 9.3. Comparison Functions

FunctionDescriptionExampleExample Result
num_nonnulls(VARIADIC "any")returns the number of non-null argumentsnum_nonnulls(1, NULL, 2)2
num_nulls(VARIADIC "any")returns the number of null argumentsnum_nulls(1, NULL, 2)1


Prev Up Next
9.1. Logical Operators Home 9.3. Mathematical Functions and Operators
epubpdf
Go to PostgreSQL 11
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp