You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dolphinscheduler.apache.org by zhuangchong <zh...@163.com> on 2021/02/19 12:49:50 UTC
[Feature][API] Division of entity classes (VO, DO)
Hi
https://github.com/apache/incubator-dolphinscheduler/issues/4813 <https://github.com/apache/incubator-dolphinscheduler/issues/4813>
Describe the feature
Division of entity classes (VO, DO)
VO corresponds to the data that needs to be displayed on the page (forms), and DO corresponds to the data stored in the database (tables)
Problems Solved:
Unneeded fields will also be passed to the front-end page, which not only increases the amount of data transmission, but also may have security problems.
Some fields need to be converted but cannot be supported.
Some fields need to be displayed but do not want to appear in the database
, etc.
Do you have any good ideas, welcome to discuss？
Re:[Feature][API] Division of entity classes (VO, DO)
Posted by CalvinKirs <ac...@163.com>.
+1
A clear layered model has obvious benefits for future complex business interactions
Best wishes！
CalvinKirs
On 02/19/2021 20:49，zhuangchong<zh...@163.com> wrote：
Hi
https://github.com/apache/incubator-dolphinscheduler/issues/4813 <https://github.com/apache/incubator-dolphinscheduler/issues/4813>
Describe the feature
Division of entity classes (VO, DO)
VO corresponds to the data that needs to be displayed on the page (forms), and DO corresponds to the data stored in the database (tables)
Problems Solved:
Unneeded fields will also be passed to the front-end page, which not only increases the amount of data transmission, but also may have security problems.
Some fields need to be converted but cannot be supported.
Some fields need to be displayed but do not want to appear in the database
, etc.
Do you have any good ideas, welcome to discuss？