Re: Setting up models and postgres in django 3.1

Figured it out 3.1 is more strict about how it creates tables in postgres. The workaround I used was to put the tables into the various appname/models.py and then import them as needed when I need them. On Friday, September 25, 2020 at 12:38:19 PM UTC-5 Patrick Carra wrote: > So I have worke

Setting up models and postgres in django 3.1

So I have worked in django 2.2 where I have multiple apps that I use the same models.py file in for all of them (same meaning I make sure each one is exactly the same as the others not one single models.py). When I do migrations I have no problem with anything. When I started using django 3.1