Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 52f7d81

Browse files
authored
Merge pull request #484 from gotqn/patch-1
Returned type added
2 parents 8f1d136 + 7eaf79f commit 52f7d81

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

docs/t-sql/functions/binary-checksum-transact-sql.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,9 @@ Specifies that the computation is over all the columns of the table. BINARY_CHEC
4646

4747
*expression*
4848
Is an [expression](../../t-sql/language-elements/expressions-transact-sql.md) of any type. BINARY_CHECKSUM ignores expressions of noncomparable data types in its computation.
49+
50+
## Return Types
51+
**int**
4952

5053
## Remarks
5154
BINARY_CHECKSUM(*), computed on any row of a table, returns the same value as long the row is not subsequently modified. BINARY_CHECKSUM satisfies the properties of a hash function: BINARY_CHECKSUM applied over any two lists of expressions returns the same value if the corresponding elements of the two lists have the same type and are equal when compared using the equals (=) operator. For this definition, null values of a specified type are considered to compare as equal. If one of the values in the expression list changes, the checksum of the list also generally changes. However, there is a small chance that the checksum will not change. For this reason, we do not recommend using BINARY_CHECKSUM to detect whether values have changed, unless your application can tolerate occasionally missing a change. Consider using HashBytes instead. When an MD5 hash algorithm is specified, the probability of HashBytes returning the same result for two different inputs is much lower than that of BINARY_CHECKSUM.

0 commit comments

Comments
 (0)