Emi Matchu
2cac048158
This was a bit tricky! When I initially turned it on, running `rails swf_assets:manifests:load` would trigger database errors of "oh no we can't get a connection from the pool!", because too many records were trying to concurrently save at once. So now, we give ourselves the ability to say `save_changes: false`, and then save them all in one batch after! That way, we're still saving by default in the edge cases where we're downloading and saving a manifest on the fly, but batching them in cases where we're likely to be dealing with a lot of them! |
||
|---|---|---|
| .. | ||
| rocketamf_extensions | ||
| tasks | ||
| fragment_localization.rb | ||
| pretty_param.rb | ||