Can't get data out - HELP, PLEASE! Options

[emeyer]

I've been trying to get the results out of the ALA Web Design Survey, and can't. When I try to download a CSV file, I get a network error in Safari and Firefox just downloads a zero-byte 'results.php.csv' file. wget times out while trying to download the file due to it getting no response. I removed the access control to the results so I could use cURL, but when I use this:

curl 'http://aneventapart.com/webdesignsurvey/results_csv.php?sid=2&export_type=1' -m 3600 -o 'results.csv'

...I get this in response after about 75 seconds have elapsed:

curl: (52) Empty reply from server

...or, on occasion, I get this after less than 75 seconds:

<table width="70%" align="center" cellpadding="0" cellspacing="0">
<tr class="grayboxheader">
<td width="14"><img src="http://aneventapart.com/webdesignsurvey/templates/Default/images/box_left.gif" border="0" width="14"></td>
<td background="http://aneventapart.com/webdesignsurvey/templates/Default/images/box_bg.gif">Error</td>
<td width="14"><img src="http://aneventapart.com/webdesignsurvey/templates/Default/images/box_right.gif" border="0" width="14"></td>
</tr>
</table>
<table width="70%" align="center" class="bordered_table">
<tr>
<td class="error">Error in query: Incorrect key file for table '/tmp/#sql_288c_0.MYI'; try to repair it</td>
</tr>
<tr>
<td align="center">
[ <a href="http://aneventapart.com/webdesignsurvey/index.php">Main</a>
]
</td>
</tr>
</table>

I'd really, really like to get the data out so it can be analyzed. Nothing I do seems to work. Help, please!

[emeyer]

Well, we finally got the data out.

Of course, to do so, we had to do a MySQL dump and then import the dumped data onto a local machine. Then we had to edit GREATEST to COALESCE. Finally, after running the whole thing through a step-tracer, we discovered that we had to up the PHP memory limit to 512MB, because even with COALESCE the special_classes lines in question looped enough to make PHP5 run completely out of memory at its default configuration. (Under PHP4, even setting the limit to 512MB was not enough; PHP still died with the results described earlier in this thread, and in about the same amount of time.)

I don't know that there's anything you can do about that for future releases, but we thought you ought to know. Hopefully you'll see this.