Accounting Sequence

build Migration considerations

• Raw `cr.execute()` INSERT/UPDATE/DELETE bypasses the ORM (no compute/constrains/tracking/mail): `WITH duplicated_sequence AS ( SELECT name, journal_id, state FROM account_move WHERE state = 'posted' AND name != '/' GROUP BY journal_id, name, state HAVING COUNT(*) > 1 ), to_update AS ( SELECT move.id, move.name, move.journal_id, move.state, move.date, row_number() OVER(PARTITION BY move.name, move.journal_id ORDER BY move.name, move.journal_id, move.date) AS row_seq FROM duplicated_sequence JOIN account_move move ON move.name = duplicated_sequence.name AND move.journal_id = duplicated_sequence.journal_id AND move.state = duplicated_sequence.state ), new_vals AS ( SELECT id, name || ' (' || (row_seq-1)::text || ')' AS name FROM to_update WHERE row_seq > 1 ) UPDATE account_move SET name = new_vals.name FROM new_vals WHERE account_move.id = new_vals.id;` - re-check the table/column names still match after upgrading. migration-raw-sql-write · source

Migration review checklist, not a compatibility verdict. No target version is selected: apply version-specific advice only when migrating to that version or later.