0.9.4

README.md

@@ -21,7 +21,7 @@ English | [中文](./README_zh_CN.md)
     -   Output DTO, used as return for complex queries
     -   Input DTO, used as parameter for complex saves
     -   Specification DTO, used as parameter for complex queries
-    -   Automatically generated DTO types or objects can be directly used by DSL. In other words, no standalone DTO solution can be as convenient as the DTOs natively supported by the ORM itself
+    -   The DTO supported by the ORM itself can be seamlessly integrated without introducing additional logic into business code.
 -   Query arbitrary graph structures
     -   No "N + 1" problem
     -   Objects at any level can be incomplete
@@ -33,6 +33,7 @@ English | [中文](./README_zh_CN.md)
     -   Automatically translates constraint violation exceptions
     -   Saved objects at any level can be incomplete
     -   Can save either entities directly or input DTOs
+    >   This section has undergone a major upgrade, and the documentation is actively being restructured. Please refer to the `save-command` examples in the accompanying examples.
 -   Powerful caching
     -   Multi-layer caching, technology for each cache layer can be freely chosen
     -   Not just object caching *(associations, computed values, multiple views)*

README_zh_CN.md

@@ -21,7 +21,7 @@
     -   Output DTO，用作复杂查询的返回
     -   Input DTO, 用作复杂保存的参数
     -   Specification DTO, 用作复杂查询的参数
-    -   自动生成的DTO类型读或对象可以直接被DSL操作。即，任何独立的DTO方案都无法如ORM自身支持的DTO一样便捷
+    -   ORM自身支持的DTO可以与其无缝集成，不会为业务代码引入额外逻辑
 -   查询任意图结构
     -   没有`N + 1`问题
     -   任何层次的对象都可以不完整
@@ -32,7 +32,8 @@
     -   每一层的多个对象都用批量DML操作
     -   自动翻译违背约束的异常
     -   任何层次的被保存对象都可以不完整    
-	-   既可以直接保存实体，也可保存Input DTO
+    -   既可以直接保存实体，也可保存Input DTO
+    > 这部分经过了大升级，文档在积极重构中，可以先看配套例子中关于save-command的例子
 -   强大的缓存
     -   多级缓存，每一级缓存都可以做自由技术选型
     -   不仅仅是对象缓存 *(关联、计算值、多视图)*