On Mon, 2007-04-02 at 01:47 +0200, Neboj=?UTF-8?B?xaE=?=a =?UTF-8?B?xJA=?=or=?UTF-8?B?xJE=?= evi=?UTF-8?B?xIcg?= wrote: > I'm writing Serbian stuff for the localflavour but I'm not sure about > following: > > How much of the information goes in there? Just the validation or we can > also put some the models there? I'm thinking to add cities with postal and > area codes and this data is more suitable for the database table than choice > list.
Some background... All the existing local flavors put these things in as static choice lists. The logic being that they do not change over time. I can see the logic of putting really large amounts of information in the database, rather than storing it in memory. I would probably do the same thing if I was trying to validate Australian postcodes against cities. To answer your query... My impresions is that this isn't appropriate for the localflavor/ section, since it is meant to be for form data validation. We have managed to keep that separate from the database backend so far. My preference would be not to go overboard here -- validate that the cities and postcodes are spelt correctly and have the right numeric format and leave it at that. Otherwise there is just no end to the amount of data people will want to include in Django. So I'm -1 on using the database to store anything (or including so much data that that becomes necessary). It would be interesting to hear other opinions, though. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
