Bug #37815
Object are not persisted
| Status: | Closed | Start date: | 2012-06-07 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 1.1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | FLOW3 version affected: | FLOW3 1.1.0 beta 2 | |
| Votes: | 0 |
Description
With the following injected repository
/**
* Team repository
*
* @var \Familiefejden\Domain\Repository\TeamRepository
* @FLOW3\Inject
*/
protected $teamRepository;
and calling the function
$this->teamRepository->add($newTeam);
i expect to have my $newTeam (a valid!) object persisted, but nothing is persisted. I get forward to my next action ($this->forward(..)) with no exceptions.
Query log remains empty.
./flow3 doctrine:update commands works perfectly and tables are created
Related issues
| related to TYPO3.Flow - Bug #37574: ReflectionData is not regenerated automatically | Resolved | 2012-07-26 |
History
Updated by Soren Malling 12 months ago
ChristianM told me on IRC, that running ->persistAll() persists the values - but nothing is persisted if not running this command
Updated by Soren Malling 12 months ago
Tried to debug the issue and added some systemlogger->log call and all of a sudden (after rebuilding proxy classes - did a flow3:cache:flush --force) the injected repository was able to persist (without running persistAll)
Updated by Karsten Dambekalns 11 months ago
- Project changed from TYPO3 Flow Base Distribution to TYPO3.Flow
- Status changed from New to Accepted
- Assignee set to Karsten Dambekalns
Updated by Karsten Dambekalns 11 months ago
- Category set to Persistence
- Status changed from Accepted to Closed
- Target version set to 1.1
- % Done changed from 0 to 100
- Has patch set to No
Persistence works fine, judging from your description (it worked all of a sudden) I guess you fell victim to #37574…