mirror of
https://github.com/postgres/postgres.git
synced 2025-07-09 22:41:56 +03:00
Change TRUE/FALSE to true/false
The lower case spellings are C and C++ standard and are used in most parts of the PostgreSQL sources. The upper case spellings are only used in some files/modules. So standardize on the standard spellings. The APIs for ICU, Perl, and Windows define their own TRUE and FALSE, so those are left as is when using those APIs. In code comments, we use the lower-case spelling for the C concepts and keep the upper-case spelling for the SQL concepts. Reviewed-by: Michael Paquier <michael.paquier@gmail.com>
This commit is contained in:
@ -676,8 +676,8 @@ ExecIndexEvalRuntimeKeys(ExprContext *econtext,
|
||||
* ExecIndexEvalArrayKeys
|
||||
* Evaluate any array key values, and set up to iterate through arrays.
|
||||
*
|
||||
* Returns TRUE if there are array elements to consider; FALSE means there
|
||||
* is at least one null or empty array, so no match is possible. On TRUE
|
||||
* Returns true if there are array elements to consider; false means there
|
||||
* is at least one null or empty array, so no match is possible. On true
|
||||
* result, the scankeys are initialized with the first elements of the arrays.
|
||||
*/
|
||||
bool
|
||||
@ -756,8 +756,8 @@ ExecIndexEvalArrayKeys(ExprContext *econtext,
|
||||
* ExecIndexAdvanceArrayKeys
|
||||
* Advance to the next set of array key values, if any.
|
||||
*
|
||||
* Returns TRUE if there is another set of values to consider, FALSE if not.
|
||||
* On TRUE result, the scankeys are initialized with the next set of values.
|
||||
* Returns true if there is another set of values to consider, false if not.
|
||||
* On true result, the scankeys are initialized with the next set of values.
|
||||
*/
|
||||
bool
|
||||
ExecIndexAdvanceArrayKeys(IndexArrayKeyInfo *arrayKeys, int numArrayKeys)
|
||||
|
Reference in New Issue
Block a user