bad query: INSERT INTO "account_journal" ("active", "alias_id", "bank_account_id", "bank_statements_source", "book_group_id", "check_add_debit_button", "check_manual_sequencing", "code", "color", "company_id", "create_date", "create_uid", "currency_id", "default_account_id", "default_sheet_mapping_id", "direct_debit_format", "direct_debit_merchant_number", "discriminate_taxes", "invoice_reference_model", "invoice_reference_type", "l10n_ar_afip_pos_number", "l10n_ar_afip_pos_partner_id", "l10n_ar_afip_pos_system", "l10n_ar_is_pos", "l10n_cl_point_of_sale_name", "l10n_cl_point_of_sale_number", "l10n_cl_point_of_sale_type", "l10n_latam_manual_checks", "l10n_latam_use_documents", "l10n_uy_type", "loss_account_id", "mail_template_id", "nacha_company_identification", "nacha_destination", "nacha_immediate_destination", "nacha_immediate_origin", "nacha_origination_dfi_identification", "name", "payment_sequence", "profit_account_id", "qr_code", "qr_code_label", "refund_sequence", "restrict_mode_hash_table", "sale_activity_note", "sale_activity_type_id", "sale_activity_user_id", "sequence", "settlement_account_id", "settlement_partner_id", "settlement_tax", "show_on_dashboard", "store_id", "suspense_account_id", "tax_settlement", "type", "write_date", "write_uid") VALUES (true, NULL, NULL, 'file_import_oca', NULL, false, false, 'NCI', 0, 10, '2024-08-21 16:37:41.047411', 2, NULL, 2984, NULL, NULL, NULL, 'no', 'odoo', 'invoice', 0, 117, NULL, false, NULL, 0, NULL, false, false, 'manual', NULL, NULL, NULL, NULL, NULL, NULL, NULL, 'Sales NCI', false, NULL, NULL, NULL, false, false, NULL, NULL, NULL, 10, NULL, NULL, NULL, true, NULL, NULL, NULL, 'sale', '2024-08-21 16:37:41.047411', 2) RETURNING "id"
ERROR: duplicate key value violates unique constraint "account_journal_code_company_uniq"
DETAIL:  Key (company_id, code)=(10, NCI) already exists.

bad query: DELETE FROM ir_attachment WHERE id IN (
            SELECT id FROM ir_attachment WHERE id in (1643) FOR NO KEY UPDATE SKIP LOCKED
        )
ERROR: could not serialize access due to concurrent update

bad query: UPDATE "account_payment" SET "message_main_attachment_id" = 1699, "write_date" = '2024-08-21 18:26:14.927370', "write_uid" = 2 WHERE id IN (9)
ERROR: could not serialize access due to concurrent update

bad query: INSERT INTO "account_payment" ("amount", "automatic", "batch_payment_id", "card_id", "cashbox_session_id", "create_date", "create_uid", "currency_id", "destination_journal_id", "direct_debit_mandate_id", "force_amount_company_currency", "installment_id", "is_internal_transfer", "l10n_latam_check_bank_id", "l10n_latam_check_id", "l10n_latam_check_issuer_vat", "l10n_latam_check_payment_date", "move_id", "paired_internal_transfer_payment_id", "partner_bank_id", "partner_id", "partner_type", "payment_group_id", "payment_method_line_id", "payment_token_id", "payment_type", "tax_withholding_id", "withholding_base_amount", "withholding_number", "write_date", "write_uid") VALUES ('-10000.00', false, NULL, NULL, NULL, '2024-08-21 18:29:59.036168', 2, 20, NULL, NULL, '0.00', NULL, false, NULL, NULL, NULL, NULL, 191, NULL, NULL, 115, 'supplier', 6, 134, NULL, 'outbound', NULL, '0.00', NULL, '2024-08-21 18:29:59.036168', 2) RETURNING "id"
ERROR: new row for relation "account_payment" violates check constraint "account_payment_check_amount_not_negative"
DETAIL:  Failing row contains (16, null, 191, null, null, 134, null, 20, 115, null, null, null, 2, 2, outbound, supplier, null, -10000.00, null, null, null, f, 2024-08-21 18:29:59.036168, 2024-08-21 18:29:59.036168, null, null, null, null, null, null, null, null, null, 0.00, null, null, null, null, null, null, null, null, 6, 0.00, null, null, null, null, null, null, f, null, null, null, null, null, null, null, null, null, null).

bad query: 
                WITH visitor AS (
            INSERT INTO website_visitor (
                partner_id, access_token, last_connection_datetime, visit_count, lang_id,
                website_id, timezone, write_uid, create_uid, write_date, create_date, country_id)
            VALUES (
                NULL, 'a9a45548c35c7336c20e0732f0636168', now() at time zone 'UTC', 1, 1,
                1, NULL, 4, 4,
                now() at time zone 'UTC', now() at time zone 'UTC', (
                    SELECT id FROM res_country WHERE code = NULL
                )
            )
            ON CONFLICT (access_token)
            DO UPDATE SET
                last_connection_datetime=excluded.last_connection_datetime,
                visit_count = CASE WHEN website_visitor.last_connection_datetime < NOW() AT TIME ZONE 'UTC' - INTERVAL '8 hours'
                                    THEN website_visitor.visit_count + 1
                                    ELSE website_visitor.visit_count
                                END
            RETURNING id, CASE WHEN create_date = now() at time zone 'UTC' THEN 'inserted' ELSE 'updated' END AS upsert
        , 'https://69914-16-0-all.runbot.adhoc.com.ar/' AS url, 4 AS page_id
                ), track AS (
                    INSERT INTO website_track (visitor_id, url, page_id, visit_datetime)
                    SELECT id, url, page_id::integer, now() at time zone 'UTC' FROM visitor
                )
                SELECT id, upsert from visitor;
ERROR: could not serialize access due to concurrent update

bad query: UPDATE "ir_property" SET "write_date" = '2024-08-22 12:59:43.534173', "write_uid" = 2 WHERE id IN (441)
ERROR: could not serialize access due to concurrent update

bad query: UPDATE "ir_property" SET "write_date" = '2024-08-22 12:59:46.217640', "write_uid" = 2 WHERE id IN (441)
ERROR: could not serialize access due to concurrent update

bad query: UPDATE "ir_property" SET "write_date" = '2024-08-22 13:01:01.905757', "write_uid" = 2 WHERE id IN (441)
ERROR: could not serialize access due to concurrent update

bad query: DELETE FROM "hr_salary_rule" WHERE id IN (17, 18, 19, 21, 20, 2, 22, 23, 4, 5, 6, 3, 7, 8)
ERROR: update or delete on table "hr_salary_rule" violates foreign key constraint "hr_payslip_line_salary_rule_id_fkey" on table "hr_payslip_line"
DETAIL:  Key (id)=(2) is still referenced from table "hr_payslip_line".