• “Unable to Open Database File”
• “Unable to Write to Database File”

Found a lot of SQLite users complaining about this, then finally got the tip from this page that I needed to set my permissions on the parent director to writeable by the Apache user too.  What a pain.

Another note: One nice thing that alleviates some of the normal irritation when moving between dev environments and production is the following code I added into the settings.py file:

import os.path
PROJECT_DIR = os.path.dirname(__file__)
DATABASE_NAME = os.path.join(PROJECT_DIR, "database.db")

Enjoy!

I wanted to be able to populate my Django models from an external script by simply calling MyObject.save() .  My particular case was scraping some information off of a website using BeautifulSoup then inserting it into my Django application, where it would show up and be editable from the admin section.  It turned out that I had a major problem with environment variables, so after a lot of reading and some trial and error, the following should work for you.

import os
import sys

sys.path.append('/path/to/the/directory/above/your/project')
os.environ['DJANGO_SETTINGS_MODULE'] = 'yourproject.settings'
from  yourproject.yourapp.models import YourModel

To be a little more clear: f your project is in “/Users/username/myproject”, append “/Users/username” to your system path.  This clears up your environment so that when you set the location of your django settings file using the dot notation, it knows where to look.

As always, if you have any questions or comments or a better way to do this, let me know.  I’m using this on Snow Leopard with a trunk SVN checkout of Django.

One major irritant I spent most of the morning working through, however, was something I think needs to be attended to, or at least clarified in the documentation.  I’ve got a model “Client” that can have more than one address “Address”, defined as a ForeignKey relationship.  I want to allow editing of the addresses inline for convenience, but kept getting pushback from the GUI when I’d try to just add in a client without an address.

Turns out, the Django automatic admin interface detects the presence/absence of fields in the inline widget to decide whether or not to validate the input.  In other words, if you’re putting any value into any of your Address’ fields, it will validate them.  Because I was using a “USStateField()” type on my model, it was always putting in a value for the state, hence it was always failing the validation b/c I wasn’t putting in other fields.

Man, very frustrating.  Replacing “USStateField()” with a “models.CharField(max_length=2)” did the trick but I don’t think it was clear at all what was happening.

Anyone who has solved this more elegantly, please get in touch.