Best practices as to when to use fields.selection vs fields.many2one

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

CRM
e-Commerce
회계
재고 관리
PoS
Project
MRP

All apps

모든 게시물 사용자 배지

태그 (모두 보기)

odoo accounting v14 pos v15

게시판 정보

도움말

Best practices as to when to use fields.selection vs fields.many2one

orm model fields.many2one design

1 회신

7023 화면

john5000

I've seen a model that has a status or state field which is done as fields.selection() and I've seen it done as a fields.many2one(). Both ways of doing it seem to work fine and do the job.

I suppose many2one is best when you expect to have new values to add over time.

I am wondering if there are any best practices as to which should be used under what cirmustances. And what are the advantages and disavantages of each. Or any notable experince in using one or the other.

Jérémy Kersten (jke)

Hello Best practice according to me is to use : many2one : for relations with another object (wich can be edited... add choice, ...) Eg: Category, manager, ... Selection : A static list (not evolutive). Eg: Status (Open / WIP / Close) JKE

john5000

작성자

Thank you jke, that is simple and makes sense.

Ivan

베스트 답변

I wouldn't say that this is best practices, but here are some "differences" that would be your consideration points when making the design decision:

selection is a fixed list once rendered (this also applies to many2one fields which is viewed with widget="selection"), you cannot apply domain to it
selection will be pulled altogether at once when HTML is rendered (this also applies to many2one fields which is viewed with widget="selection"). Not a good choice if you have hundreds or thousands selection.
selection fields (this does NOT apply to many2one fields viewed with widget="selection") is not stored as a Foreign Key. So you can remove an entry from the selection and no integrity problem will ensue.

As for the states, you can still make it a selection field whilst making it dynamic by supplying the entries from a table. Selection field can accept a function as selection source.

토론이 재미있으신가요? 직접 참여해보세요!

지금 바로 가입하여 독점 서비스를 이용해보고 특별한 커뮤니티와 소통하세요!

가입

관련 게시물	답글	화면
How i can verify record then save in Odoo 12? orm model	0 9월 19	3469
Get model data in a controller 해결 완료 orm model controller	4 10월 21	37640
How do I dump all the fields and values in a model (ideally including those from relationships)? 해결 완료 development orm model	1 10월 20	12558
Usage of ORM methods and ORM API documentation? database orm model	1 3월 15	5044
why res.config model in odoo is TransientModel not Model ? wizard orm model TransientModel	1 8월 25	3808

신고된 질문입니다

토론이 재미있으신가요? 직접 참여해보세요!