Damien Elmes bd1c6d4395 more robust anki1 upgrading & anki2 importing ... - base the 2.0 model id on the 1.2 one so we don't get new models each time we reimport the file - when determining if we can reuse an existing note, it must have the same model id, and the model must have the same schema - make sure we check templates when determining schema - if schema has diverged, note needs new guid		2012-10-27 20:55:08 +09:00
..
anki2-alpha.anki2	add upgrade unit test	2012-03-12 12:42:26 +09:00
anki12-due.anki	on upgrade all cards of a note should share the same due #	2012-04-06 12:45:01 +09:00
anki12.anki	ensure duplicate model creation times are accounted for	2011-08-26 22:33:24 +09:00
diffmodels1.anki	more robust anki1 upgrading & anki2 importing	2012-10-27 20:55:08 +09:00
diffmodels2.anki	more robust anki1 upgrading & anki2 importing	2012-10-27 20:55:08 +09:00
fake.png	update unit tests for sqlalchemy drop	2011-04-28 09:23:53 +09:00
invalid-ords.anki	work around invalid 1.2 decks with multiple templates sharing same ord	2012-10-24 13:11:18 +09:00
media.apkg	handle conflicts in apkg import as well	2012-09-21 15:42:30 +09:00
mnemo.db	foreign card importing; mnemosyne 2.0 importer	2012-03-07 05:45:52 +09:00
supermemo1.xml	update unit tests for sqlalchemy drop	2011-04-28 09:23:53 +09:00
text-2fields.txt	update unit tests for sqlalchemy drop	2011-04-28 09:23:53 +09:00
text-tags.txt	update unit tests for sqlalchemy drop	2011-04-28 09:23:53 +09:00
text-update.txt	when updating, preserve unmapped fields	2012-03-25 02:07:20 +09:00