epam / edp-ddm-architecture

Apache License 2.0
5 stars 2 forks source link

Запит не відповідає данному xml, немає прикладу результату #76

Closed scorpio-84 closed 11 months ago

scorpio-84 commented 11 months ago

https://github.com/epam/edp-ddm-architecture/blob/cca09714aef3d5f2e21eac11e41fce4c72a17696/docs/ua/modules/registry-develop/pages/study-project/study-tasks/task-1-registry-db-modeling.adoc?plain=1#L451-L476

antontuhai commented 11 months ago

Thank you for bringing this to our attention.

We've thoroughly tested your request, and it functions as anticipated. To clarify:

Given the Search Condition XML:

<changeSet author="registry owner" id="searchCondition koatuu_obl_contains_name"> 
     <ext:createSearchCondition name="koatuu_obl_contains_name"> 
         <ext:table name="koatuu" alias="k"> 
             <ext:column name="koatuu_id"/> 
             <ext:column name="code"/> 
             <ext:column name="name" sorting="asc" searchType="contains"/> 
         </ext:table> 
         <ext:where> 
             <ext:condition tableAlias="k" columnName="type" operator="eq" value="'О'"/> 
         </ext:where> 
     </ext:createSearchCondition> 
</changeSet> 

A VIEW is created in the database. This translates to the SQL query code as detailed in our documentation:

SELECT k.koatuu_id, 
       k.code, 
       k.name 
  FROM koatuu k 
 WHERE k.type = 'О'::text 
 ORDER BY k.name; 

Having addressed the matter, we are now closing this issue. I appreciate your understanding.