Small. Fast. Reliable.
Choose any three.
*** 1,5 ****
  The document describes default date and time functions in SQLite.
! This document is a suppliment to the
  function documentation found on the
  {link: /lang_expr.html#corefunctions SQL Expression Syntax} page.
  
--- 1,5 ----
  The document describes default date and time functions in SQLite.
! This document is a supplement to the
  function documentation found on the
  {link: /lang_expr.html#corefunctions SQL Expression Syntax} page.
  
***************
*** 168,181 ****
  -- e_  It is so. --drh
  
  _[Consider instead, using localtime_r which is reentrant and may be used
! *without* expensive mutex locking. Altough non-standard it's available
  on most Unixes --hauk]_ But it is not available on windows, as far as I
! am aware. --drh On winodws localtime() is thread-safe if the MT c runtime is used. The MT runtime uses thread locale storage for the static variables ,this kind of functions use.--gr _[What about using localtime_r, and on systems where it
  is unavailable defining it as sqliteOsEnterMutext() ; locatime() ; sqliteOsLeaveMutex()
  so that non-windows systems get the maximum advantage, with almost zero
  code impact?]_ -- AdamBerger
  
! Date computations do not give correct results for dates before julian
  day number 0 (-4713-11-24 12:00:00).
  
  All internal computations assume the Gregorian calendar system.
--- 168,181 ----
  -- e_  It is so. --drh
  
  _[Consider instead, using localtime_r which is reentrant and may be used
! *without* expensive mutex locking. Although non-standard it's available
  on most Unixes --hauk]_ But it is not available on windows, as far as I
! am aware. --drh On windows localtime() is thread-safe if the MT C runtime is used. The MT runtime uses thread-local storage for the static variables, the kind functions use.--gr _[What about using localtime_r, and on systems where it
  is unavailable defining it as sqliteOsEnterMutext() ; locatime() ; sqliteOsLeaveMutex()
  so that non-windows systems get the maximum advantage, with almost zero
  code impact?]_ -- AdamBerger
  
! Date computations do not give correct results for dates before Julian
  day number 0 (-4713-11-24 12:00:00).
  
  All internal computations assume the Gregorian calendar system.