Comments on: Processing malformed files with FasterCSV

By: Chris Habgood

Chris Habgood — Tue, 01 Nov 2011 22:46:21 +0000

Eric, what would that look like?

By: Eric Davis

Eric Davis — Fri, 19 Aug 2011 20:41:55 +0000

That really does look nasty. I’m wondering if it would be better to use #parse inside of a begin/rescue block and then just work with each row as an Array outside of FasterCSV.

By: Tom

Tom — Thu, 30 Jun 2011 19:42:28 +0000

But how do you actually capture the offending row so you can at least log it? You would think something like output.gets or something, but I can’t figure it out. Not a big fan of FasterCSV at this point.

By: James

James — Sun, 17 Apr 2011 08:00:57 +0000

thanks for the solution. Its a cool way to get around it but imo FasterCSV is just not cool.

By: Mike Boone

Mike Boone — Mon, 31 Jan 2011 03:05:05 +0000

Thanks for the idea. The foreach syntax seems so convenient until you actually need to deal with errors. Wish there was a simpler way!

By: Kyle Burckhard

Kyle Burckhard — Wed, 04 Aug 2010 21:30:13 +0000

Matthew, I just wanted to thank you for your code bit. I ran into the same problem with FasterCSV today and this really helped.