Hi Shawn, I had already looked at fixtures and the reason I disregarded it is because the documentation says:
"Every time you run loaddata the data will be read from the fixture and re-loaded into the database. Note that this means that if you change one of the rows created by a fixture and then run loaddata again you'll wipe out any changes you've made." So, it seems that means one of two things. Either I'll have to keep a single fixture, which on every update just gets longer, or a directory full of arbitrarily named fixtures (for uniqueness). Both, I'd like to avoid. I guess this depends on whether it's necessary to retain each fixture permanently after import. Do you know this? I'd be fine with a solution that necessitates a fixture for import but then would allow me to delete it immediately afterwards (irregardless of backup practices). Also, my data won't be in YAML or JSON. Does MySQL or Sqlite offer an export option that'll do this? Thanks and sorry if all of this is common knowledge for everyone else. Kevin On Dec 22, 12:13 pm, Shawn Milochik <sh...@milochik.com> wrote: > Fixtures sound like the way to go. > > You should get what you need from > here:http://docs.djangoproject.com/en/dev/howto/initial-data/ > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
