This change updates the local development restore operation to update the
ar_internal_metadata table if it's present, setting the environment
value to development.
Previously, failing to update the environment metadata would result in a potentially alarming error that might cause users to believe they were about to perform a destructive operation against their production database when what was actually happening was that the development database was a snapshot taken from production.
If the table is not present (either for older Rails applications or
non-Rails applications), this anonymous PG function will no-op.
This change updates the local development restore operation to update the
ar_internal_metadata
table if it's present, setting the environment value todevelopment
.Previously, failing to update the environment metadata would result in a potentially alarming error that might cause users to believe they were about to perform a destructive operation against their production database when what was actually happening was that the development database was a snapshot taken from production.
If the table is not present (either for older Rails applications or non-Rails applications), this anonymous PG function will no-op.
Fix #147