Feature #10360
Make option handling in persistence backends more flexible
Status: | Resolved | Start date: | 2010-10-21 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
Category: | Persistence | |||
Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 13 | Estimated time: | 1.00 hour | |
PHP Version: | Complexity: | |||
Has patch: |
Description
I would not skip NULL values in all cases, but only of no setter exists. That way you can set existing settings to NULL. For non-existant setters a warning could be logged (at least in dev context), so you have a chance to notice errors.
Associated revisions
[+FEATURE] FLOW3 (Persistence): More flexible handling of backend options
Now unknown backend options are ignored if the value is NULL. This way
you can still set valid settings to NULL. For non-existent setters a
warning is logged (debug level).
Change-Id: If84583e806058a2c9c3482f26c1dd418b91601a8
Resolves: #10360
History
#1 Updated by Karsten Dambekalns almost 5 years ago
- Status changed from Needs Feedback to Under Review
#2 Updated by Karsten Dambekalns almost 5 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset a39924d6a06f93f7f5a02c5bcfcb31924ef9fdda.