v5:datetime:datetime_index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
v5:datetime:datetime_index [2016/04/14 01:38] – mnewnham | v5:datetime:datetime_index [2019/01/02 02:56] – [Introduction] mnewnham | ||
---|---|---|---|
Line 9: | Line 9: | ||
Dates from 100 A.D. to 3000 A.D. and later have been tested. The minimum is 100 A.D. as <100 will invoke the | Dates from 100 A.D. to 3000 A.D. and later have been tested. The minimum is 100 A.D. as <100 will invoke the | ||
- | 2 => 4 digit year conversion. The maximum is billions of years in the future, but this is a theoretical limit as the computation of that year would take too long with the current implementation of adodb_mktime(). | + | 2 => 4 digit year conversion. The maximum is billions of years in the future, but this is a theoretical limit as the computation of that year would take too long with the current implementation of adodb_mktime(). Since version 5.20.13, the future date cutoff is limited to 200 years by default. This value is controlled by a constant which may be modified for user requirement. |
===== Functions Replaced ===== | ===== Functions Replaced ===== | ||
Line 54: | Line 54: | ||
ADOdb date/time library does not support daylight savings time but you can write [[v5: | ADOdb date/time library does not support daylight savings time but you can write [[v5: | ||
===== Function Descriptions ====== | ===== Function Descriptions ====== | ||
- | ^ Function | + | ^ Function |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
- | | [[v5: | + | | [[v5: |
v5/datetime/datetime_index.txt · Last modified: 2023/05/18 18:49 by dregad