I added it to settings model (good idea) but it must also remain here in this form, if you run db:migrate on new database, initializers are executed just once during env load and that one loading default data is skipped if settings table does not exist yet so we don't have default settings at this moment and then calling SETTINGS[:fix_db_cache] = true will fail since the new setting is invalid (missing description etc)