Skip ke Konten
Menu
Pertanyaan ini telah diberikan tanda
1 Balas
7048 Tampilan

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.

 

Avatar
Buang

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

Penulis

Thank you jke, that is simple and makes sense.

Jawaban Terbai

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.

Avatar
Buang
Post Terkait Replies Tampilan Aktivitas
0
Sep 19
3496
4
Okt 21
37665
1
Okt 20
12597
1
Mar 15
5066
1
Agu 25
3847