Bug #6028
DataMapper cannot handle wrongly typed input.
| Status: | Resolved | Start date: | 2010-01-14 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 7 | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
When a property value comes back from the persistence depths as string, but is supposed to be an integer (or some other type), it is processed as string. That leads to problems when persisting again and changes data, which obviously should not happen.
Associated revisions
[+BUGFIX] FLOW3 (Persistence): DataMapper now typecasts values to the intended type when mapping properties. Fixes #6028.
[+BUGFIX] FLOW3 (Persistence): DateTime properties being NULL can be persisted now. Fixes #6029.
[+BUGFIX] FLOW3 (MVC): Removed some strtolower() calls in Router to enable consistently cased template folders. Fixes #6030.
History
#1 Updated by Karsten Dambekalns over 5 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r3633.