Because it's been a while since I added one.

A Manager is the interface through which database query operations are provided to Django models. At least one Manager exists for every model in a Django application.

The way Manager classes work is documented in Making queries; this document specifically touches on model options that customize Manager behavior.

By default, Django adds a Manager with the name objects to every Django model class. However, if you want to use objects as a field name, or if you want to use a name other than objects for the Manager, you can rename it on a per-model basis. To rename the Manager for a given class, define a class attribute of type models.Manager() on that model.

To represent database-table data in Python objects, Django uses an intuitive system: A model class represents a database table, and an instance of that class represents a particular record in the database table.

To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database.

You import the model class from wherever it lives on the Python path, as you may expect. (We point this out here because previous Django versions required funky model importing.)

Here is another post. It's short.

Here is my second blog post. I want it to be wordy, so here's a few quotes:

"I believe in God, but not as one thing, not as an old man in the sky. I believe that what people call God is something in all of us. I believe that what Jesus and Mohammed and Buddha and all the rest said was right. It's just that the translations have gone wrong."
-- John Lennon

"One of the things I learned the hard way was that it doesn' t pay to get discouraged. Keeping busy and making optimism a way of life can restore your faith in yourself."
-- Lucille Ball

"By letting it go it all gets done. The world is won by those who let it go. But when you try and try. The world is beyond the winning."
-- Lao Tzu