Re: Is it time to start sqlite3 DB from scratch?
If it's dummy data then you can always wipe it and reset South.
There are some issues with sqlite. Not all constraints are enforced and
it doesn't support removing fields, for two biggies. So you can't delete
a field from a model (the migration will fail), and you can't use the
'unique_together' meta feature either. It will never raise an error and
it'll let you put duplicate records in.
A lot of people develop locally with sqlite for the convenience then
deploy PostgreSQL for a robust DB.
To answer your questions:
1. If you're going to wipe the DB and start over then you're already set.
However, if you want to start South from scratch (it'll make your tests
run faster because you'll have fewer migrations), you can do this:
A: ./manage.py reset south
B: rm appname/migrations/*
C: ./manage.py convert_to_south appname
2. If you wipe the DB it'll obviously destroy all data and you'll have
to reload. You could export fixtures first, but restoring them will
depend on whether they were tied to your app's data.
3. No.
4. Not if you're not worried about losing any data.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home