How about having a SingletonModel in Django?

Question

I'm making a very simple website in Django. On one of the pages there is a vertical ticker box. I need to give the client a way to edit the contents of the ticker box as an HTMLField.

The first way that came to mind was to make a model Ticker which will have only one instance. Then I thought, instead of making sure manually that only one instance exists, perhaps there is (or there should be) something like a SingletonModel class in Django, which is like a normal model, except it makes sure no more than one instance gets created?

Or perhaps I should be solving my problem in a different way?

Answer 1

rewrite your save method so that every time a Ticker object gets saved it overwrites the existing one (if one exists).

Answer 2

I think having a "singleton" model is ugly; it's dumb use of the relational database and it's bad UI, because the admin UI is built around working with lists of objects.

Instead I prefer to use a generic solution like django-chunks or django-flatblocks for this.