Closed MerielP closed 8 years ago
Please take another look at this issue. The crash should now be fixed but I think the crash was simply masking an underlying problem. The implication I draw from this issue is that the upload should have worked - the crash tells me it didn't. When you perform this test again, please let me know the exact date and time when the error happens so I can check logs.
I've just tried this again on Dev (in the database 'Testing CSV upload and new table creation' in 'Sample project'). It still didn't work, but this time I got this error message:
I tried this twice, and the same thing happened both times. The clock on my computer said 10.44.
Please try now. I am not happy with my fix but it will be useful to see if the fix does work for you.
Hurrah! This now seems to be working.
To reproduce this bug, find an old database (I am guessing that in this context, 'old' means created before the ODBC work) that has at least one CSV file uploaded to it, on either Dev or Staging. Try to upload another CSV file. The result is a distinctly unfriendly error message.
This doesn't happen with newly created databases, and doesn't seem to be an issue at all on App. My guess is therefore that this is another instance of something having been broken by the ODBC work.
(Marked critical on James's advice - needs fixing before the new version is deployed to App.)