From 241557f7b1b3bd75bba03e97da3fffa80bc9e65c Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:52:11 +0000 Subject: [PATCH] Clarifications to MAXREC/overflow Add "where possible" to the MAXREC section in acknowledgement of the fact that not all output formats support overflow flagging. Add a crossreference from the Overflow section back to the MAXREC section. --- DALI.tex | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/DALI.tex b/DALI.tex index beb2ee3..6b49286 100644 --- a/DALI.tex +++ b/DALI.tex @@ -1126,7 +1126,7 @@ \subsubsection{MAXREC} enforce a limit on the value of MAXREC that is smaller than the value in the request. If the size of the result exceeds the resulting limit, the service must only return the requested number of rows. If the result set is truncated in this -fashion, it must include an overflow indicator as specified in Section \ref{sec:response-overflow}. +fashion, it must include an overflow indicator where possible as specified in Section \ref{sec:response-overflow}. The service must support the special value of MAXREC=0. This value indicates that, in the event of an otherwise valid request, a valid response be returned @@ -1427,7 +1427,8 @@ \subsubsection{Overflow} \verb|text/tab-separated-values| do not support indicating overflow. In general, services may truncate the output results when reaching a limit. A default or -user-specified value of the MAXREC parameter is a common mechanism that causes truncation +user-specified value of the MAXREC parameter defined in Section \ref{sec:MAXREC} +is a common mechanism that causes truncation of results, but service providers may also impose limits in services that do not use MAXREC and indicate that the limit was reached with the overflow indicator.