Skip to content

[18.0][FIX] se_index: update constrain to unique 'name' instead of lang+model#227

Merged
OCA-git-bot merged 1 commit into
OCA:18.0from
akretion:18-0-FIX-se_index_constrain_name
Mar 19, 2026
Merged

[18.0][FIX] se_index: update constrain to unique 'name' instead of lang+model#227
OCA-git-bot merged 1 commit into
OCA:18.0from
akretion:18-0-FIX-se_index_constrain_name

Conversation

@arnaudlayec

Copy link
Copy Markdown
Contributor

Before, the previous constrain was preventing 2 indexes on the same Odoo model
This change allow this behavior, by keeping the security of not having 2 indexes with same name in Odoo (which is the point to verify for consistency with the Search Engine).

Exemple: from res.partner, I want to push to a Search Engine 2 indexes: one "companies", another one "persons".
=> This PR allows it.

[FIX] se_index: update constrain to unique 'name' instead of lang+model

[FIX] se_index: update constrain to unique 'name' instead of lang+model

@sebastienbeau sebastienbeau left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (code review)

@arnaudlayec arnaudlayec changed the title [FIX] se_index: update constrain to unique 'name' instead of lang+model [18.0][FIX] se_index: update constrain to unique 'name' instead of lang+model Mar 18, 2026
@sebastienbeau

Copy link
Copy Markdown
Member

/ocabot merge patch

@OCA-git-bot

Copy link
Copy Markdown
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 18.0-ocabot-merge-pr-227-by-sebastienbeau-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit fea6314 into OCA:18.0 Mar 19, 2026
7 checks passed
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at 99eccd3. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants