Comments on: Ruby on Rails: Import CSV data into database http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/#utm_source=feed&utm_medium=feed&utm_campaign=feed These are my experiences making Technology work Tue, 23 Mar 2010 23:41:17 +0000 http://wordpress.org/?v=abc hourly 1 By: Darren http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-431 Darren Tue, 23 Mar 2010 23:41:17 +0000 http://goodbadtech.com/?p=43#comment-431 Forgot to mention in my last comment but if you push this to a background job you should do some (rescue FasterCSV::MalformedCSVError) action. Or even better do it if not tossing to background job so you don't get app errors if users upload a file that isn't parsed perfectly. Forgot to mention in my last comment but if you push this to a background job you should do some (rescue FasterCSV::MalformedCSVError) action. Or even better do it if not tossing to background job so you don’t get app errors if users upload a file that isn’t parsed perfectly.

]]> By: /good/bad/tech http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-430 /good/bad/tech Tue, 23 Mar 2010 21:42:04 +0000 http://goodbadtech.com/?p=43#comment-430 Thanks for the feedback. I'm glad it helped you out. Thanks for the feedback. I’m glad it helped you out.

]]> By: Greg http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-429 Greg Fri, 19 Mar 2010 12:50:49 +0000 http://goodbadtech.com/?p=43#comment-429 Just implemented for a project.  Works great.  Many thanks for the work.   Just implemented for a project.  Works great.  Many thanks for the work.
 

]]> By: Darren http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-428 Darren Wed, 24 Feb 2010 20:20:16 +0000 http://goodbadtech.com/?p=43#comment-428 Err I meant model Err I meant model

]]> By: Darren http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-427 Darren Wed, 24 Feb 2010 09:34:35 +0000 http://goodbadtech.com/?p=43#comment-427 In regards to moving the logic into the controller: http://gist.github.com/313281 This is just a quick example and I'm not sure it would work perfect. My setup is quite a lot different, but a good  starting point. Also error handling could be done a few ways. For me first I'm using delayed_job and after a csv file is uploaded I past off the load to delayed_job b/c we have imports of 100,000 + lines. As load_csv method is looping over rows we collect errors, if any, into an array and send out the results in an email. In regards to moving the logic into the controller: http://gist.github.com/313281
This is just a quick example and I’m not sure it would work perfect. My setup is quite a lot different, but a good  starting point.
Also error handling could be done a few ways. For me first I’m using delayed_job and after a csv file is uploaded I past off the load to delayed_job b/c we have imports of 100,000 + lines. As load_csv method is looping over rows we collect errors, if any, into an array and send out the results in an email.

]]> By: /good/bad/tech http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-425 /good/bad/tech Tue, 23 Feb 2010 19:31:59 +0000 http://goodbadtech.com/?p=43#comment-425 Hi John, I'm glad the post was helpful and that you already tracked down answer for the question you had. Regards, Spencer Hi John,

I’m glad the post was helpful and that you already tracked down answer for the question you had.

Regards,
Spencer

]]> By: John McLeod http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-423 John McLeod Wed, 17 Feb 2010 18:56:47 +0000 http://goodbadtech.com/?p=43#comment-423 Found it. My routes were messed up. map.import_proc '/import/proc/id', :controller => 'imports', :action => 'proc_csv' should be... map.import_proc '/import/proc/:id', :controller => 'imports', :action => 'proc_csv' John Found it.
My routes were messed up.
map.import_proc ‘/import/proc/id’, :controller => ‘imports’, :action => ‘proc_csv’
should be…
map.import_proc ‘/import/proc/:id’, :controller => ‘imports’, :action => ‘proc_csv’
John

]]> By: John McLeod http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-422 John McLeod Wed, 17 Feb 2010 18:41:56 +0000 http://goodbadtech.com/?p=43#comment-422 I can replace Line 11 with... <%= link_to "process", :controller => 'imports', :action => 'proc_csv', :id => @import.id %> and everything works fine. John I can replace Line 11 with…
<%= link_to “process”, :controller => ‘imports’, :action => ‘proc_csv’, :id => @import.id %>
and everything works fine.
John

]]> By: John McLeod http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-421 John McLeod Wed, 17 Feb 2010 16:25:27 +0000 http://goodbadtech.com/?p=43#comment-421 Hello, Thanks for the tutorial, it helped extremely. I do have a little problem. The import is created but the proc_csv does not. I get an ... "<code>undefined method `to_sym' for nil:NilClass" error on the Imports/show view - Line 11.</code> <code>8: 9: <% else %> 10: 11: <%= link_to "process", import_proc_path(@import.id) %> 12: 13: <% end %> Thank you for any help with this. John </code> Hello,
Thanks for the tutorial, it helped extremely.
I do have a little problem.
The import is created but the proc_csv does not.
I get an …
“undefined method `to_sym' for nil:NilClass" error on the Imports/show view - Line 11.
8:
9: <% else %>
10:
11: <%= link_to "process", import_proc_path(@import.id) %>
12:
13: <% end %>

Thank you for any help with this.

John

]]> By: Sai http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/comment-page-1/#comment-420 Sai Fri, 05 Feb 2010 00:55:56 +0000 http://goodbadtech.com/?p=43#comment-420 Ah, thank you for clarifying this. What are the benefits of <% .save! %> over <% .save %>? I thought the validations would have been run regardless. Also, save! appears to raise ActiveRecord::RecordInvalid, as opposed to the neater error_messages which are available via the view. Is it possible to raise a neater error message? As far as I can tell, it isn't, but I may be wrong. Ah, thank you for clarifying this. What are the benefits of <% .save! %> over <% .save %>? I thought the validations would have been run regardless.
Also, save! appears to raise ActiveRecord::RecordInvalid, as opposed to the neater error_messages which are available via the view. Is it possible to raise a neater error message? As far as I can tell, it isn’t, but I may be wrong.

]]>