Thanks Antonis, and great post on production databases. I'll definately be switching to postgresql. I come from php/xamp and I liked the MySQL GUI with phpMyAdmin so I've gravitated towards MySQL since.
On Thursday, August 17, 2017 at 2:05:44 PM UTC-6, Antonis Christofides wrote: > > Hello, > > My opinion is that you should definitely switch to PostgreSQL, although > I'm not aware whether this would make migrating easier. I've written a > relatively > long post > <https://djangodeployment.com/2016/12/23/which-database-should-i-use-on-production/> > > about which database to choose in production. > > Second, just to make things clear, the word "migration" has two meanings. > The original meaning of migration is to switch to another software system > (e.g. migrate from MySQL to PostgreSQL, or migrate a repository from > subversion to git). In Django, the term "migration" means something else: > to update the database to the new schema. In my opinion this terminology is > wrong and confusing (apparently it comes from Ruby on Rails, but I'm not > certain), and a better one would have been "dbupdate" or something, but > since it's migration we'll keep it and you'll have to understand which > meaning is meant in each case. > > What your problem is cannot be understood with your general exposition, > however after you gain a little bit of experience with migrations you > shouldn't have any such problems. Migrations are tricky to understand but > once you do they work flawlessly. The next time you have a problem give us > some information with the exact error message so that we can explain what's > wrong. > > Regards, > > Antonis > > Antonis Christofideshttp://djangodeployment.com > > On 2017-08-17 20:10, Alexander Joseph wrote: > > I'm pretty new to django and I've been having problems with > makemigrations/migrate and I wonder if Im doing things right. > > I'm using MySQL backend and after reading in the documentation a little it > sounds like Postgresql might make migrating more painless. Usually my > problems stem from changing table fields, adding new tables/models, and > migrating both on my development server and my production server > (PythonAnywhere) > > More than once I've had to drop my database, delete all my migrations, and > start over with initial migrations on the development server. This wont fly > for long on production though of course .. once I actually have users and > data. > > I'm wondering if I should switch to postgresql or if theres any further > resources that you might know of that would help me out? Thanks > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users...@googlegroups.com <javascript:>. > To post to this group, send email to django...@googlegroups.com > <javascript:>. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/16d60ab0-51e8-42a3-8f42-f4753f0adda3%40googlegroups.com > > <https://groups.google.com/d/msgid/django-users/16d60ab0-51e8-42a3-8f42-f4753f0adda3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/ffe78757-1809-4b86-949c-a30e257163be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
