Problem of Data Maintenance screen automatic generation. about opentouryo

[daisukenishino]

Other test case should be confirmed.

• Table with a composite key
  Also Confirm that there is no problem if the composite key is present in the table.
• SQL other than SELECT/JION
  • Please confirm there is no problem if you use "single table of the SELECT that not use JOIN clause".
  • Note
    • It isn't this function's prerequisite that using multiple tables.
    • This function have purpose that the search screen and the update screen is generated by from free SQL.
• Columns that do not conform to the naming rules for update by this function.
  • This function applies a naming rules as [TableName.ColumnName] at the column to be updated.
  • Therefor, Columns that do not conform to the naming rules will not be an update target of this function.

[daisukenishino]

Shortage of specification

• How to Specify which table will be deleted. In the current specification, the updated table is also a deleted table. The way for specify as table that updated but not deleted is required.
• When you want to exclude the table from the insert and update the target, then you disobey the naming rules of this function.

[daisukenishino]

About the features

"Data Maintenance screen automatic generation" function is different from the "Table Maintenance screen automatic generation" function.

• "Table Maintenance screen automatic generation" function to use the DDL (DBMS Metadata) as input information.
• "Data Maintenance screen automatic generation" function is to use the SELECT statement (free SQL) as input information.

About the test case

I hope that the following SELECT statement (free SQL) will be tested.

• The number of selected table.
  • In the case of 1 table is selected
  • In the case of 2 table is selected (joined)
• Naming rules of column
  • If the column is follow the naming rules, the column is updated.
  • If the column does not follow the naming rules, the column is not updated.

[SandeepNayak077]

@daisukenishino

HODC understood that 'free SQL' means 'dynamic queries written in .xml' files
For example:

• Dao[TableName]_D2_Select.xml (In the case of 1 table is selected)
• Dao[TableA]_[TableB]_JOIN_S2_Select.xml (In the case of 2 table is selected (joined))

Please confirm our understanding

[daisukenishino]

@SandeepNayak077

Your recognition correct.
But, I think that I want to increase the accuracy more,
Please write an example of SQL that is described in two XML at here.

• TableName_Select.xml (In the case of 1 table is selected)
• TableA_TableB_JOIN.xml (In the case of 2 table is selected (joined))

[SandeepNayak077]

@daisukenishino

Thank you for the response.
HODC will write an proper example of SQL and confirm the test cases on the two XML that the XML queries should follow the naming rules as [TableName.ColumnName] at the column level.

[daisukenishino]

@SandeepNayak077

Please also reference to the following issue.
See : OpenTouryoProject/OpenTouryoDocuments#10