30,997
edits
Language and development rules: Difference between revisions
Jump to navigation
Jump to search
m
→Communication between business logic - data (ORM)
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 576: | Line 576: | ||
More "purist" on paper (closer of business), this method also has the disadvantage of being more complex in practice. | More "purist" on paper (closer of business), this method also has the disadvantage of being more complex in practice. | ||
Example: This is the choice if you use the ORM Framework '''Propel''' ( | Example: This is the choice if you use the ORM Framework '''Propel''' (https://propelorm.org/). We find this model in heavier applications, based on this ORM among others. | ||
-> For Dolibarr development, the pattern used is the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating technical architecture. It is by this way that the development, understanding of code and technical maintenance and / or business | -> For Dolibarr development, the pattern used is the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating technical architecture. It is by this way that the development, understanding of code and technical maintenance and / or business behavior seems the more productive (this is however an ongoing debate between the purists and the pragmatists, debate in which nobody can really be right, because it depends on the objectives). | ||
[[Category:Development]] | [[Category:Development]] | ||