discourse

Commit Graph

Author	SHA1	Message	Date
Daniel Waterworth	55a1394342	DEV: pluck_first Doing .pluck(:column).first is a very common pattern in Discourse and in most cases, a limit cause isn't being added. Instead of adding a limit clause to all these callsites, this commit adds two new methods to ActiveRecord::Relation: pluck_first, equivalent to limit(1).pluck(*columns).first and pluck_first! which, like other finder methods, raises an exception when no record is found	2019-10-21 12:08:20 +01:00
Gerhard Schlager	d686318133	FIX: Prevent failed remaps during restores Additional changes: * Verbose logging of remaps during restores * Exclude the backup_metadata table from restores	2019-08-12 17:15:01 +02:00
Gerhard Schlager	a65a9a85d5	FEATURE: Remap uploads during restore when S3 or CDN changes In order for this to work the Backuper stores a couple of site settings in the new backup_metadata table, because the old setting values might not be available on restore anymore.	2019-07-09 14:04:16 +02:00

Author

SHA1

Message

Date

Daniel Waterworth

55a1394342

DEV: pluck_first

Doing .pluck(:column).first is a very common pattern in Discourse and in
most cases, a limit cause isn't being added. Instead of adding a limit
clause to all these callsites, this commit adds two new methods to
ActiveRecord::Relation:

pluck_first, equivalent to limit(1).pluck(*columns).first

and pluck_first! which, like other finder methods, raises an exception
when no record is found

2019-10-21 12:08:20 +01:00

Gerhard Schlager

d686318133

FIX: Prevent failed remaps during restores

Additional changes:
* Verbose logging of remaps during restores
* Exclude the backup_metadata table from restores

2019-08-12 17:15:01 +02:00

Gerhard Schlager

a65a9a85d5

FEATURE: Remap uploads during restore when S3 or CDN changes

In order for this to work the Backuper stores a couple of site settings
in the new backup_metadata table, because the old setting values might
not be available on restore anymore.

2019-07-09 14:04:16 +02:00

3 Commits