On Tue, Mar 31, 2009 at 8:52 PM, DenesL <[email protected]> wrote: > > On Mar 31, 6:58 pm, Yarko Tymciurak <[email protected]> wrote: > > On Tue, Mar 31, 2009 at 2:40 PM, mdipierro <[email protected]> > wrote: > > > > > I do not think the CSV formatting belongs in the model. There may be > it was only a suggestion, it has to be tied to the field somehow > > > > difference places in an app where importing is done suing different > > > conventions. And why for csv and not xml? etc. > then use it for all, call it field.import_filter, it is the developer > responsibility to set it if he/she does not want the default behavior > (e.g. convert null to None in csv imports). > > > > > I agree w/ Massimo... > > > > Also, you can find "smart" date parsing strategies in Python Cookbook; > see > > python dateutil... > you are putting to much emphasis on the example, the functionality can > be anything you want/need: conversions, packing, data cleanup, etc. Of > course all can be done externally but why not allow an "inside web2py" > version too?. > Or I could we completely wrong...
The Python Cookbook says a bit about why this is not a good idea for production sites.... too many special cases, I think... > > > Denes > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
