Laurent Desausoi
7593c073d2
Before this commit the neutralize system introduced in v16 was using ORM
methods in order to change appropriate records. Although flexible, this approach
could lead to call some methods with side effects while neutralizing
(eg: overloads of write).
This patch converts the neutralize system to a safer "inert" SQL based approach
by migrating the generic method _neutralize to SQL files exposed in the
data folder.
Task id: 2961687
closes odoo/odoo#102792
X-original-commit: e5dbded9bb363351feff7ca8a56c7f8a6860f492
Related: odoo/enterprise#32580
Signed-off-by: Fabien Meghazi <fme@odoo.com>
20 lines
455 B
SQL
20 lines
455 B
SQL
-- deactivate mail servers
|
|
UPDATE ir_mail_server
|
|
SET active = false;
|
|
|
|
-- deactivate crons
|
|
UPDATE ir_cron
|
|
SET active = false
|
|
WHERE id NOT IN (
|
|
SELECT res_id
|
|
FROM ir_model_data
|
|
WHERE model = 'ir.cron'
|
|
AND name = 'autovacuum_job'
|
|
);
|
|
|
|
-- neutralization flag for the database
|
|
INSERT INTO ir_config_parameter (key, value)
|
|
VALUES ('database.is_neutralized', true)
|
|
ON CONFLICT (key) DO
|
|
UPDATE SET value = true;
|