[EMAIL PROTECTED] wrote:
> I could create a model and then only have one row, but that seems > clunky. I did exactly this and overrode the .save() method so that the model was constrained to only have one row by resetting self.id to 1 in the .save() (I think...). Effect was that if you added a second row in the admin - and this is the only clunkiness I perceived - you just got one row with your new data. You could also edit the existing one row. Barry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
