![]() ![]() Manage.py dumpdata -traceback > data.json Do you get any extra output if you run it with traceback? manage.py dumpdata -traceback > data.json See the new attach. Python manage.py dumpdata > backedup_data.json -exclude app_name Python manage.py dumpdata -indent=2 -v 2 -traceback gigs `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,ĪLTER TABLE `gigs_gig` ADD CONSTRAINT `venue_id_refs_id_3d901b6d` FOREIGN KEY (`venue_id`) REFERENCES `gigs_venue` (`id`) ĪLTER TABLE `gigs_gig` ADD CONSTRAINT `location_id_refs_id_2f8d7a0` FOREIGN KEY (`location_id`) REFERENCES `gigs_location` (`id`) COMMIT Return u"%s on %s at %s" % (, self.date, ) Url = models.URLField(max_length=60, verify_exists=False, blank=True, null=True) # because of single thread problems, I left this off ()ĭate = models.DateField(blank=True, null=True)ĭetails = models.CharField(max_length=250, blank=True, null=True) Name = models.CharField(max_length=120, blank=True, null=True)Ĭontact = models.CharField(max_length=250, blank=True, null=True) ![]() usr/local/lib/python2.6/site-packages/MySQLdb/_init_.py:34: DeprecationWarning: the sets module is deprecatedĮrror: Unable to serialize database: Location matching query does not exist. ![]() Previous Post Next Post $ python manage.py dumpdata -indent=2 gigs > fixtures/gigs_100914.json
0 Comments
Leave a Reply. |