Sylvain Lemiere
Sylvain Lemiere
I'm seeing this as well, @gtmax have you tried your code in a production environment ?
@anhkind I am seeing the same thing, I am on rails 3.2.22.1 and ruby 2.2.4. Using a `Octopus.using` block do solve the issue
upon further inspection I figured that the issue is that the after_initialize callback that set the current_shard of the owner (https://github.com/thiagopradi/octopus/blob/master/lib/octopus/model.rb#L107) is called after the ensure of using_shard has reverted...
The problem is not really that I will persist the object to the database but more that I will act on the record based on the wrong information. For instance...
@dylanahsmith do you have any feedback on the above ? Thanks a lot !
For us this happened because of a mismatch between uuid and integer ids. Basically we were calling the fetch method with a device UUID (something like `9d2e4c7c-cb79-41ad-9c14-3a805f3d23a9`) when it was...
I'm happy to make the necessary changes in that PR to make the raising behavior happen without the configuration option.