Re: Is it time to start sqlite3 DB from scratch?

You're welcome. To clarify, South is wonderful. It's sqlite that is the problem. The migrations only fail because sqlite doesn't support all normal SQL commands. I love sqlite, but it's not always the best solution. -- You received this message because you are subscribed to the Google Groups

Re: Is it time to start sqlite3 DB from scratch?

The solution appears the have been simple: delete the offending tables. I have not tried to upload an actual image yet yet everything appears 9knock wood) to be working properly thus far. Thanks for the advice, especially about how South isn't so friendly with sqlite3! On Mar 2, 10:02 pm, DF

Re: Is it time to start sqlite3 DB from scratch?

Thanks. I'm having a bear of a time after I added an ImageFile and media folder and then tried to make a migration with South (made another post about this). I figure it might be best to just chuck it and start again. On Mar 2, 9:59 pm, Shawn Milochik wrote: > On 03/02/2012

Re: Is it time to start sqlite3 DB from scratch?

On 03/02/2012 09:55 PM, DF wrote: Thanks. Still not sure how to wipe the database before starting fresh with South. If it's a sqlite database you just delete the file. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,

Re: Is it time to start sqlite3 DB from scratch?

Thanks. Still not sure how to wipe the database before starting fresh with South. On Mar 2, 8:50 pm, Shawn Milochik wrote: > 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

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