On 4/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > 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.
The django.contrib.localflavor package is for any and every snippet of Django code that could be useful for a specific country / location, so it's not *just* limited to Form-related logic. For example, django.contrib.localflavor.usa.us_states contains some helpful data structures that people can use in their own applications, independent of Form code. But I agree with Malcolm that there should be some sort of limit to the amount of data that we should include in there. If you want to contribute some data that is so massive that it would best fit in a database, it might not be the best candidate for localflavor. Also, I'm not sure it makes sense to put models in localflavor, because models are the types of things that people tend to want to have control over, and we end up making subframeworks that let people customize (see, for example, the User.get_profile() stuff). Neboja, does that help? If you're still unsure, it might help if you gave more specifics on what sort of information/logic you wanted to include. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
