SQLite Forum

Doc enhancements for new release
Login
Firstly, this is shaping up to be a landmark release - well done and also thank you for the great work.

Some suggested documentation enhancements for the current DRAFT docs.

In [draft/lang_mathfunc.html](https://sqlite.org/draft/lang_mathfunc.html):

- In the preamble:  
  *Current*: "..or strings or blobs that looks like integers..."  
  *Suggest*: "..or strings or blobs that look like integers..."  
  *Reason* : Grammar

- ceil(x)  
  *Current*: "Return the next larger representable integer values above X."  
  *Suggest*: "Return the first representable integer value equal to or above X."  
  *Reason* : ceil(7) == 7 (not some next value above 7).  

- floor(x)
  *Current*: "Return the next representable integer value that is less than X."  
  *Suggest*: "Return the first representable integer value equal to or less than X."  
  *Reason* : floor(7) == 7 (not some next value below 7).  

- trunc(x)  
  *Current*: "Return the first representable integers on the line from X to 0.0. This is similar to ceiling(X) and floor(X) except that it always rounds toward zero."  
  *Suggest*: "Removes the fraction of a number leaving only the Integer part. This is similar to floor(X) for positive numbers, and ceiling(X) for negative numbers, in that it always rounds toward zero."  
  *Reason* : It feels more accurate to the math *and* to the meaning of "Truncate" where this function name is born from.  

- pow(X,Y)  
  *Current*: "Compute X raised to Y-th power."  
  *Suggest*: "Compute X raised to the power Y."  
  *Reason* : Style - Not really wrong, but every other reference to Y on that document is the pure form, like the suggested.  


In [draft/lang_altertable.html](https://sqlite.org/draft/lang_altertable.html#altertabdropcol):

- ALTER TABLE DROP COLUMN (In the reasons it may fail):  
  *Current*: "The column appears in a table CHECK constraint. However, the column being deleted can be used in a column CHECK constraint because the column CHECK constraint is dropped together with the column itself."  
  *Suggested*: "The column appears in a table CHECK constraint. However, the drop is allowed if the only such CHECK constraint is declared within the column itself, since such a constraint is dropped along with the column."  
  *Reason* : Clarity


Thanks,
Ryan