Further options for Importing/Exporting/Merging data in the WU History Database.

[GoogleCodeExporter]

What enhancement are you proposing?

A way to export the Completed WU .CSV file to .txt or other format.

What is the expected output for the proposed enhancement?

To be able to read the full list of completed WU's and the important info that 
Stanford Folding@Home can analyze. 

What version of the product are you using?

0.6.2

Original issue reported on code.google.com by xNBKxZ...@gmail.com on 8 May 2011 at 1:15

[GoogleCodeExporter]

I' m expanding this request to encompass more options for importing and 
exporting.  Would like to use a plug-in architecture to allow other to write 
their own plugins for import and export.

Original comment by harlam357 on 4 Aug 2011 at 6:46

• Changed title: Further options for Importing/Exporting/Merging data in the WU History Database.
• Added labels: Component-Logic, Component-Persistence, OpSys-Linux, OpSys-Windows, Usability

[GoogleCodeExporter]

Original comment by harlam357 on 4 Aug 2011 at 6:46

[GoogleCodeExporter]

I didn't know you were using csv still, since you have sqlite as dependency I 
expected the work unit history to be stored in an sql db. To me this seems 
quite useful as some of the statistical data you could obtain through the 
stored work units are easier I think with sql select statements then done in 
memory ( easier meaning less code required, and less memory needed )?

Original comment by mtm78.cf...@gmail.com on 12 Jan 2012 at 3:35

[harlam357]

Closed - export to .csv was added in 0.9.6