Adrian Holovaty wrote: > On 3/15/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
>> Example: the string representation of a date in may depend on the >> locale of the remote user, which the model knows nothing about. The >> conversion from string to datetime will need to happen in a layer >> that is aware of the HTTP request context. (This is a somewhat >> contrived example due to the abysmal state of international datetime >> formatting/parsing in the Python standard library, but I'm sure there >> are other examples). > > In this example, the view code would perform that logic -- not the > model layer. The model layer is only responsible for *critical* > validation logic that applies to *every instance of the model, ever* > -- not special-cases. For special cases, you'll use a custom > form/manipulator, just like before. yes, i agree. the only problem for me is: is the string-to-date auto-conversion a *critical* validation-part? gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
