From 83518b7ed98e52c288c54c9db4d3470f9a63b628 Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Thu, 16 May 2024 06:31:10 -0400 Subject: [PATCH] Escape less than sign --- RFC-0001-nan-definition.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/RFC-0001-nan-definition.md b/RFC-0001-nan-definition.md index 6b1e3d57..2101e0b1 100644 --- a/RFC-0001-nan-definition.md +++ b/RFC-0001-nan-definition.md @@ -58,10 +58,10 @@ and E is the value of the , then M * 10E is the apparent value of ANL. Some read the above as disallowing NaNs because floating point types are defined only as mantissa and exponent, and there are no special values defined like NaN, infinity, and -infinity. I don't think it's clear one way or the other, and it looks like most databases do support NaN values. -With regard to sorting, the ANSI spec says the following: > -> f) PVi is said to precede QVi if the value of the “PVi QVi” is True for the applicable . +With regard to sorting, the ANSI spec says the following: +> f) PVi is said to precede QVi if the value of the <comparison predicate> “PVi <comp op> QVi” is True for the applicable <comp op>. > -> g) If PVi and QVi are not the null value and the result of “PVi QVi” is Unknown, then the relative ordering of PVi and QVi is implementation-dependent. +> g) If PVi and QVi are not the null value and the result of “PVi <comp op> QVi” is Unknown, then the relative ordering of PVi and QVi is implementation-dependent. ### Current Presto behavior