Re: Django 1.9 ./manage.py migrate error

Thanks for the assistance so far. Reading https://docs.djangoproject.com/en/1.9/topics/migrations/ it says I should be able to run migrate to apply migrations. But does this mean I have to manually do something, or should that work the same as it did on 1.8? I am assuming that it should also be

Re: git exclude files

On Saturday, December 12, 2015 at 7:38:21 AM UTC-8, Gary Roach wrote: > > Unfortunately, venv doesn't give me a choice as to where the files are > stored. They are all under the top directory of the same name as the > project but are actually in the same directory as the top level project > fold

Re: Django 1.9 ./manage.py migrate error

Is there a reason you can't use migrations? --run-syncdb is really only meant for huge projects (hundreds or thousands of models) where migrations are too slow. Not sure why it's not working though. You'd have to project a sample project for me to debug further. On Saturday, December 12, 2015 a

Re: a bug in model.Manager.values_list?

Models and querysets are not serializeable using the default `json` tools, but Django provides its own set of tools that allow you to serialize models and querysets. Take a look at serializing django objects

Re: Django 1.9 ./manage.py migrate error

No, I haven't added any migrations. I did try with --run-syncdb though, and still had the same error though On Saturday, 12 December 2015 16:26:15 UTC+2, Tim Graham wrote: > > Does your application have migrations? Quoting the 1.9 release notes, > "Automatic syncing of apps without migrations i

Re: a bug in model.Manager.values_list?

"Its not a bug, its a feature." See: https://docs.djangoproject.com/en/1.9/ref/models/querysets/#when-querysets-are-evaluated If you were designing Django's internals, you might have decided that the Queryset "should behave" in a certain way, but the designers have chosen this approach. There

Re: git exclude files

Unfortunately, venv doesn't give me a choice as to where the files are stored. They are all under the top directory of the same name as the project but are actually in the same directory as the top level project folder. ie /root/archive/ venv files, and archive/ project. From what you say, they

Re: Populating default data into sql tables using sql file inside the sql folder of app is not working

You can use migrations and the RunSQL operation. https://docs.djangoproject.com/en/stable/ref/migration-operations/#runsql On Saturday, December 12, 2015 at 8:59:08 AM UTC-5, naveen tamanam wrote: > > In older django versions I use to load the default values using sql files > which are in the fo

Re: Django 1.9 ./manage.py migrate error

Does your application have migrations? Quoting the 1.9 release notes, "Automatic syncing of apps without migrations is removed. Migrations are compulsory for all apps unless you pass the --run-syncdb opt

Populating default data into sql tables using sql file inside the sql folder of app is not working

In older django versions I use to load the default values using sql files which are in the folder sql in side the app directory. But in django.1.9c1 it's not working. When I look at django documentation it seems like support raw sql file is removed to load the default data. How to load the daf

Tool to document project urls, views, templates, etc...

Anyone know of a tool that can analyze a project and generate a list or graph of *views* & related information? I'm maintaining a medium size Django project. For each feature/change, I am finding myself creating a "map" of the relevant view names/relationships for quick reference. This includes:

Django 1.9 ./manage.py migrate error

Hi I seem to have an issue with running migrate and have been googling all day without any luck I have an app which works and runs on 1.8 After cloning the repo and creating a new ve, I ended up with Django 1.9 Running the ./manage.py migrate creates the database, but none of the tables from t