]> source.dussan.org Git - nextcloud-server.git/commit
fix(migration): Make naming constraint fail softer on updates 43357/head
authorJoas Schilling <coding@schilljs.com>
Wed, 7 Feb 2024 19:45:51 +0000 (20:45 +0100)
committerJoas Schilling <coding@schilljs.com>
Wed, 7 Feb 2024 19:45:51 +0000 (20:45 +0100)
commit487c33f479120bf8f94970f5c26642258ebd1a62
tree49f6348c6dc6e98e1f0302e589c89f5435b88ab4
parent0395cd8716312441be9f1011a5aa12adac9555e4
fix(migration): Make naming constraint fail softer on updates

Only on installation we want to break hard, so that all developers notice
the bugs when installing the app on any database or CI, and can work on
fixing their migrations before releasing a version incompatible with Postgres.

In case of updates we might be running on production instances and the
administrators being faced with the error would not know how to resolve it
anyway. This can also happen with instances, that had the issue before the
current update, so we don't want to make their life more complicated
than needed.

Signed-off-by: Joas Schilling <coding@schilljs.com>
lib/private/DB/MigrationService.php