raise exception when salesforce returns an exception for job

[jthibeaux]

I was attempting to test things out, and struggled with some error conditions resulting in an illegal array access as opposed to a proper exception based on what came back from Salesforce. This pull request is to simply raise an exception when Salesforce returns an exception to us, rather than expecting a job ID (which is not there in some cases).

[kellydunn]

@jthibeaux , this might help address #32 , at least clients would then be able to rescue from the Exception.

Looks like it needs a rebase, though.

[yatish27]

@kellydunn Can you test the commit, I can rebase once I get a thumbs up

[jthibeaux]

Hope it helps!

[kellydunn]

@yatish27 , I can confirm that I'm getting salesforce errors now instead of the ruby exception.

[yatish27]

Can @jthibeaux Update the PR with latest Master will merge it then

[jthibeaux]

Updated

[yatish27]

rebasing and updating the gem

On Mon, Aug 25, 2014 at 11:25 AM, Jeremy Thibeaux [email protected]
wrote:

Updated

Reply to this email directly or view it on GitHub
#26 (comment)
.

Yats

[yatish27]

@jthibeaux Can you check if master is stable and issue is resolved. If yes i will updated the gem version and publish

[jthibeaux]

I am actually not in a good position to support this change as I am not
currently using salesforce_bulk_api.

On Sat, Sep 6, 2014 at 9:17 PM, Yatish Mehta [email protected]
wrote:

@jthibeaux https://github.com/jthibeaux Can you check if master is
stable and issue is resolved. If yes i will updated the gem version and
publish

—
Reply to this email directly or view it on GitHub
#26 (comment)
.