From: Nigel K. <sup...@pe...> - 2008-06-26 08:42:58
|
> I cannot see any problems in the Access table that could cause some kind of > error condition but the export stops at exactly the same record every time > and suspiciously close to when it creates a 100MB csv file (104140795) so > could I be hitting a memory allocation limit or am I totally off-the-mark? > >Could be... Hard to tell, but I don't think so... > >I have looked at you patch... > >You do know that your "-L" is only active when you do not also specify "-Q", >right? > >I cannot see any obvious errors in your code. > >It's time for debugging: valgrind, gdb. > >Anyway: I think it is a much cleaner solution to post-process your >generated SQL (using awk) to produce the output needed; thereby >seperating the two responsibilities: DB conversion and Data manipulation. > >Jarl Thanks for the feedback - the export runs if I remove two rows/records in the database so it looks like there is a small corruption which I can easily fix. Not sure if its worth the time to find out what's tripping the export and make sure its trapped as the problem only occurs with 1 table out of 25 I am exporting. Thanks also for the comments on my first ever 'c' coding! Nigel |