On Mon, Apr 27, 2009 at 2:31 PM, Tim Michelsen <[email protected]>wrote:
> > Hello, > > > About fields like: [Timmie, LLC] - are you having a problem? Have > > you tried this? > Actually not yet. You asked for changes based on something you hadn't tried yet? Try first.... I do not like you suggested change... dialects already encapsulate these parameters (csv module already provides the class); I once quickly tried a more general version: def export_to_csv_file(self, ofile, **dialect_settings) It's a bad idea for more than one reason. --- one problem is this exists in several places (SQLRows, and SQLDB), is called by __str__ function, and so is not reasonably settable this way from applications. If you follow all the call chains within to the import/export csv, and you will see. A dialect class that can be set outside of a call chain seems to be the way to handle this. - Yarko --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
