Feb'2012: at version 1.3.1
book printed in 2007 covered v0.96. There's a "web preview" available there covering the newer versions, though most of the action there seems like it's from 2009.
steps in processing a request
Mar'2011 - still doesn't use email address as identifier (instead of username) very well http://www.micahcarrick.com/django-email-authentication.html
Starting to play with it - Mar'2009
There's a book-v2 draft in-process that includes django-v1 (book currently in print doesn't cover that version).
- looks like framework code is within '/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django'
Decided it's time to try TextMate.
To run multiple projects, it looks like I set a manual port number when launching like 'python manage.py runserver 8001'.
doesn't include setup info for SQLite - see v1 book for that (or, duh, just look at the comments in the settings file)
missing 'unicode' method for Book class
More ORM joys:
Unless you instruct it otherwise, Django automatically gives every model an auto-incrementing integer primary key field called id. Each Django model is required to have a single-column primary key.
what if you want to partition your data across multiple databases/servers?
Adding null=True is more complicated than adding blank=True, because null=True changes the semantics of the database - that is, it changes the CREATE TABLE statement to remove the NOT NULL from the publication_date field. To complete this change, we'll need to update the database. For a number of reasons, Django does not attempt to automate changes to database schemas, so it's your own responsibility to execute the appropriate ALTER TABLE statement whenever you make such a change to a model.
Uh, boy, turning on the admin interface created all sorts of issues
- contrary to docs, it never asked me about creating a superuser
then when I hit url again, it said "'W S G I Request' object has no attribute 'user'"
ok, I also uncommented 'django.contrib.auth', having done 'django.contrib.auth' before; then re-ran syncdb, which then properly had me set up super-user.
argh, still getting the "'W S G I Request' object has no attribute 'user'" message
- So I also uncommented 'django.contrib.sessions', re-ran syncdb, then everything was good.
Apr23'2009: Set up Mac Personal Svn Server before going further.
Apr23 decide to jump into using PinAx, and working on a personal project
Then decide that's a distraction, and I should focus on the product and stay with the mainstream/core framework.
start fresh, following docs for 1.2.
create director/app inside Virtual Env pinax-env/mf/
- launch, hit root, it loads fine
edit settings.py file per docs (uncomment admin app line, too). Using SQLite-3. Set db NAME=~/Documents/djcode.../mf/mf.sql
run syncdb get sqlite3.OperationalError: unable to open database file
used chmod to widen permissions in that directory: no difference
tried changing file-extension to .db, then to leave it completely off: no difference
changed path to db file to be full (start with /Users/billseitz... instead of ~ - it worked. (Now have mf.db.)
as part of syncdb it asked if I wanted to set admin superuser, so I did (and this time I documented it in my Private Wiki).
need to start app within the project. It won't let you use the same name for both, so the app is family
SQL for users/accounts/payments (make this the "default")
Django And Mongodb for everything else
Outcome: get DayJob, put this on hold.