rfc:introduce-type-affinity
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:introduce-type-affinity [2015/03/16 22:12] – yohgaki | rfc:introduce-type-affinity [2021/03/27 14:50] (current) – Move to inactive ilutov | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2015-03-16 | * Date: 2015-03-16 | ||
* Author: Yasuo Ohgaki < | * Author: Yasuo Ohgaki < | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 29: | Line 29: | ||
* Detect possible data type without definition/ | * Detect possible data type without definition/ | ||
- | * Have INI option for type affinity conversion | + | * Have INI option for type affinity conversion |
* Data is stored with native data type | * Data is stored with native data type | ||
* Conversion will never raise error | * Conversion will never raise error | ||
* Provide data type definition/ | * Provide data type definition/ | ||
- | * Apply type affinity function and convert | + | * Apply type affinity function and convert |
* If there is conversion error, it may raise error | * If there is conversion error, it may raise error | ||
Line 40: | Line 40: | ||
Introduce type affinity conversion function: | Introduce type affinity conversion function: | ||
- | * void type_affinitize(mixed $input [, array $definition ]); | + | * void type_affinitize(mixed |
+ | * void type_affinitize_input(string $input=" | ||
Type affinity may be applied to any inputs including databases/ | Type affinity may be applied to any inputs including databases/ |
rfc/introduce-type-affinity.1426543922.txt.gz · Last modified: 2017/09/22 13:28 (external edit)