This is expected behaviour.
*Blob* models are intended to be immutable in spirit. One file, one blob.
And if you want to do transformations of a given Blob, the idea is that
you'll simply create a new one, rather than attempt to mutate the existing
(though of course, you can delete that later i
Hey Dan!
ActiveStorage doesn't work that way *currently*. When you call `attach` you
are creating the new blob and attachment for the object.
Only use case that ActiveStorage covers is this
https://github.com/rails/rails/blob/master/activestorage/db/migrate/20170806125915_create_active_storage_t
Hey Guillermo, please do share your patch I'm interested :)We are also
patching migrations :)
I was exploring adding sprinkles of "no-dowtime" migration to Rails in the
last few months, but I'm hitting the dead-end (for similar reasons that
Will and Xavier mentioned)
On Friday, April 20,
Maintaining Rails application both on Heroku(cloud) and on-premises I
completely understand frustrations from the post above. That being said I
don’t see easy way for Rails to manage external services such as; Database,
Redis, Elastic, etc… Maybe one area where Rails could help is ability to
