SQLite CVSTrac

*** 1,12 ****
! _By DRH on 2003-09-28_
! 
! The document describes proposed date and time functions for SQLite.
! _Update: Most of the functionality described here has been available
! since version 2.8.7, 2003-12-04.  Exceptions are noted._
  
  *Function Overview*
  
! Five date and time functions are proposed, as follows:
  
  1: date( _timestring_, _modifier_, _modifier_, ...)
  2: time( _timestring_, _modifier_, _modifier_, ...)
--- 1,11 ----
! 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 SQL Expression Syntax} page.
  
  *Function Overview*
  
! Five date and time functions are available, as follows:
  
  1: date( _timestring_, _modifier_, _modifier_, ...)
  2: time( _timestring_, _modifier_, _modifier_, ...)
***************
*** 77,89 ****
  Universal Coordinated Time (UTC) is used.
  Format 12 is the julian day number expressed as a floating point value.
  
- _Please be sure to address Ticket #415 so we get full millisecond precision in julian day numbers.
- Unfortunately this may mean adjusting some expression test cases that depend on values rounded to
- fewer digits. -- e_
- It is so. --drh
- 
- _'now' does not return milliseconds_ --kks
- 
  *Modifiers*
  
  The time string can be followed by zero or more modifiers that alter the
--- 76,81 ----
***************
*** 104,111 ****
  12: unixepoch
  13: localtime
  14: utc
- 15: julian  (not implemented as of 2004-01-05)
- 16: gregorian  (not implemented as of 2004-01-05)
  
  The first size modifiers (1 through 6) simply add the specified amount
  of time to the date specified by the preceding timestring.
--- 96,101 ----
***************
*** 125,134 ****
  The "localtime" modifier (13) adjusts the previous time string so that it
  displays the correct local time.  "utc" undoes this.
  
- The "julian" modifier (14) assumes the that the time string is a gregorian
- date and converts the date into a julian date.  "gregorian" undoes the
- work of "julian".
- 
  *Examples*
  
  Compute the current date.
--- 115,120 ----
***************
*** 192,204 ****
  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.  When
! you use the "julian" modifier, it does not convert the date into a real
! Julian calendar date, it merely shifts the Gregorian calendar date to
! align it with the Julian calendar.  This means that the "julian" modifier
! will not work right for dates that exist in the Julian calendar but which
! do not exist in the Gregorian calendar.
! Example: 1900-02-29.
  
  ***
  For my use I added new functions and functionalities to the date functions that
--- 178,184 ----
  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.
  
  ***
  For my use I added new functions and functionalities to the date functions that

sqlite - Date And Time Functions