Re: [web2py] export_to_csv_file and colnames

[howesc]

ping.  in trunk it's now at line 4774.

if there is a reason not to make the change please let me know so i can fix 
my code.  (but i assume this just has not made it to the priority list yet, 
which is just fine, it is the holiday season and all!)

thanks,

christian

[web2py] export_to_csv_file and colnames

[howesc]

Massimo and crew,

I am trying to use export_to_csv_file() on a rows object with the colnames 
parameter on google app engine.  it turns out that the method (in both 
sql.py and the new dal.py) outputs the proper column names, but then outputs 
data for every column in the table.

the culprit is on line 4741 of dal.py (from trunk):
for col in self.colnames:
should be
for col in colnames:

and then, so long as the user's colnames are in the format 
'table_name.field_name' it works as desired (at least from my 
perspective).

does this sounds correct?  if so, do you mind adding it to trunk?

thanks!

christian

Re: [web2py] export_to_csv_file and colnames

[Thadeus Burgess]

that would be a bug for sure :p

--
Thadeus




On Thu, Dec 23, 2010 at 6:59 AM, howesc how...@umich.edu wrote:

 Massimo and crew,

 I am trying to use export_to_csv_file() on a rows object with the colnames
 parameter on google app engine.  it turns out that the method (in both
 sql.py and the new dal.py) outputs the proper column names, but then outputs
 data for every column in the table.

 the culprit is on line 4741 of dal.py (from trunk):
 for col in self.colnames:
 should be
 for col in colnames:

 and then, so long as the user's colnames are in the format
 'table_name.field_name' it works as desired (at least from my
 perspective).

 does this sounds correct?  if so, do you mind adding it to trunk?

 thanks!

 christian