Re: Is there a way to create a new database table other than model?

None that I know of, but I am no Django guru. I get the feeling I'm missing something about your situation however. It seems like you should be able to accomplish what you want, saving unique info about each game, without per-game tables. You have a many to many relationship between games and

Re: Is there a way to create a new database table other than model?

If you absolutely need to do so, you can execute raw sql queries to do whatever you need using Django. The docs are here: http://docs.djangoproject.com/en/1.2/topics/db/sql/ However, it's probably a 'bad' idea to go mucking about with sql if

Re: DRY forms

Apologies, I seem to have misunderstood the situation in my haste to be of assistance. I admit I'm no Django/Python whiz, more of a talented(?) dabbler. Maybe someone else can correct me, but it seems that save() will always hit the entire row if you use a single model. Does save(f It seems a

Re: Database Design Question

Ok.. that wasn't really ideal, a better (and more normalized) solution might look a bit like this: Sample Table: -> sample_id (pk) -> sample_type_id (fk) -> other descriptive fields Sample Type Table: -> sample_type_id (pk) -> other descriptive fields Attribute Type Table: -> attribute_type_id