Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.2.3
-
Fix Version/s: None
-
Component/s: Behaviors, Data Fixtures, Import/Export, Searchable
-
Labels:None
-
Environment:PHP 5.3.3 / symfony 1.4.9-dev / MySQL 5.0
Description
Sample schema:
Blog:
actAs: [Versionable, Searchable]
columns:
id:
name: string
text: text
When dumping data of a schema with Versionable and/or Searchable Behaviour, the dump.yml will contain all data, including the *_version and *_index tables.
Trying to load the same .yml file results in Duplicate-Key constraint violations, as long as the data for the *_version and *_index tables is present.
The import is only successfull, when the data for these tables is discarded.
This leads to the issue, that one can only do a dump-load cycle, when the complete version history of a Model is discarded. Which makes dump-load for such models rather useless.