Bug #6029
PdoBackend cannot handle uninitialized DateTime properties
| Status: | Resolved | Start date: | 2010-01-14 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 7 | |||
| PHP Version: | Complexity: | |||
| Has patch: | FLOW3 version affected: | |||
| Votes: | 0 |
Description
Properties with a declared type of DateTime that have a NULL value break persistence, because the PdoBackend tries to use their value as DateTime object...
Related issues
| related to TYPO3.Flow - Bug #6069: PdoBackend cannot handle uninitialized SplObjectStorage p... | Resolved | 2010-01-18 |
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
Updated by Karsten Dambekalns over 3 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r3633.