taskrabbit / forklift Goto Github PK

The error message during insert is:

/Users/rahil/Sites/random/forklift/lib/forklift/transports/mysql.rb:253:in `query': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '2012-06-22 21:20:40", "2012-06-22 21:20:40", NULL, 0)' at line 1 (Mysql2::Error)

Here is the data for that row. The broken value is in scraped_email_subject (note the backslashes)

{:id=>67113, :base_listing_id=>63535, :type=>"ApplicationMethod::Scraped", :scraped_email_id=>5778, :scraped_email_subject=>"ATTN: Hiring Manager, INTERN\\", :offsite_url=>nil, :created_at=>2012-06-22 21:20:40 -0700, :updated_at=>2012-06-22 21:20:40 -0700, :override_email=>nil, :screen_offsite_apply=>0}

If I do safe_values(d.values) I get:

"67113, 63535, \"ApplicationMethod::Scraped\", 5778, \"ATTN: Hiring Manager, INTERN\\\", NULL, \"2012-06-22 21:20:40\", \"2012-06-22 21:20:40\", NULL, 0"

I'm playing around with safe_values right now trying to get a solution, just thought I'd give you a heads up @evantahler.

I am trying to use this gem in our project however it is locked to version 1 of the elasticsearch gem

 forklift_etl was resolved to 1.0.8, which depends on
      elasticsearch (>= 1.0.0, ~> 1.0)

any idea on how large of a task it is to make this compatible for use with the elasticsearch 2.0.0 version?

@rgarver and @rahilsondhi: I'm betting you folks use this tool far more than I do... want to be maintainers?

the example project within the gem should be simple, and executable by anyone. This probably involves including some see data (even a mysqldump) within the project and instructions on how to change the config.yml files to work locally.

I'm finding about 46 instances of the old 1.8 hash rocket. I propose we use the new hash syntax wherever possible.

Perhaps this should be done after we have a test suite so that we don't break anything by accident.