Naming and scoping guidelines to make apps that are actually 'pluggable'?

Hello all, Page one of the tutorial features a large picture of a lightbulb, next to a statement of Philosophy: "Django apps are 'pluggable': You can use an app in multiple projects, and you can distribute apps, because they don't have to be tied to a given Django installation." The tutori

"id may not be NULL" during save in one-to-many relationship

Hello djangoists! Code has been coming along pretty well in my first django project. But I hit a snag with a one-to-many relationship in my model. When I do something like this: f = Foo() b = Bar(foo=f) f.save() b.save() # error here I get an error like "foos_bar.foo_id may not

Re: "id may not be NULL" during save in one-to-many relationship

On Apr 7, 8:06 pm, Malcolm Tredinnick wrote: > You have to save before assigning, since the id value from > the assigned object is stored somewhere else. Think of it as "only > assign saved objects". > ... > One day we might change that, since it's a common mistake Okay, thanks. Perhaps a good

Re: "id may not be NULL" during save in one-to-many relationship

On Apr 7, 9:53 pm, Malcolm Tredinnick wrote: > At that point in the first tutorial, subtleties like > this are not of paramount importance. It's the beginner's > tutorial, not a reference document. Hrm... well, I'd argue that in a system which synchronizes database tables with in-memory objects