v5:datetime:datetime_index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
v5:datetime:datetime_index [2016/01/13 16:16] – mnewnham | v5:datetime:datetime_index [2019/01/02 03:04] – [Table] mnewnham | ||
---|---|---|---|
Line 2: | Line 2: | ||
[[v5: | [[v5: | ||
</ | </ | ||
- | ====== ADOdb Date/ | + | ====== ADOdb Date/ |
- | <WRAP alert> | + | |
- | * Support for Daylight Savings Time may not be completely implemented | + | |
- | * There may be conflicting functionality with the [[http:// | + | |
- | </ | + | |
===== Introduction ===== | ===== Introduction ===== | ||
PHP native date functions use integer timestamps for computations. Because of this, dates are restricted to the years 1901-2038 on Unix and 1970-2038 on Windows due to integer overflow for dates beyond those years. This library overcomes these limitations by replacing the native function' | PHP native date functions use integer timestamps for computations. Because of this, dates are restricted to the years 1901-2038 on Unix and 1970-2038 on Windows due to integer overflow for dates beyond those years. This library overcomes these limitations by replacing the native function' | ||
Line 12: | 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 ===== | ||
+ | ----------------------------- | ||
+ | |||
+ | <WRAP alert> | ||
+ | * Support for Daylight Savings Time may not be completely implemented, | ||
+ | * There may be conflicting functionality with the [[http:// | ||
+ | </ | ||
+ | |||
This library replaces native functions as follows: | This library replaces native functions as follows: | ||
Line 28: | Line 32: | ||
not handled currently. | not handled currently. | ||
- | This library is independant | + | This library is independent |
===== Performance ===== | ===== Performance ===== | ||
Line 47: | Line 51: | ||
*/ | */ | ||
</ | </ | ||
+ | ===== Daylight Savings Time ===== | ||
+ | ADOdb date/time library does not support daylight savings time but you can write [[v5: | ||
+ | ===== Future Date Cutoff ===== | ||
+ | For security reasons, the maximum future date that can be generated is defaulted to 200 years in the future. This is controlled by the constant '' | ||
===== 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: | ||
v5/datetime/datetime_index.txt · Last modified: 2023/05/18 18:49 by dregad