id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
8507	dumpdata/loaddata can't handle two of the same contenttypes having different IDs in different databases	Erik Allik <eallik@…>	nobody	"Currently loaddata and dumpdata are pretty dumb in that they are not able to identify when two objects/rows that have different database ID's are actually one and the same object (or equivalent).

For example, when dumping a dataset that has fkeys to the django_content_type table and then loading that data to another database which happens to have exactly the same content types installed but some of which have different database ID values, the outcome is an IntegrityError (or corrupted data). I think users should actually be able to do that without having to concern themselves with low level details such as database IDs.

As a potential solution, it could be possible define how two model objects compare two be able to match equivalent objects with different ID's.

As a side note, this could actually evolve to something that would also allow for callbacks to determine whether to overwrite a database object with an fixture object or not (for example, based on modification dates). This would simplify synchronizing databases and would not be difficult to implement either. "		closed	Core (Serialization)	dev		duplicate	dumpdata loaddata	eallik@…	Unreviewed	0	0	0	0	0	0