1. In the database manual 2.18 table, the table T_titemactteTeacher corresponds to the TITEMATHODBO, and in the original UnionPay code, there is already a TITEMATHODBO class, in this class code, the table is looking for T_TITEMATHOD, exactly That kind, is it to modify the code, or executed according to the database manual?
2. Is the question of the case for this? As described above 2.18.
3. In Table 2.18, a field in the manual is Tearhcerid, which should be compared to TeacherID according to the literal understanding.
4. Depending on the specification, the BO in Table 2.17 should be wrong, and should be TITEMACTIOBJECTBO, based on this, I created the corresponding VO.
5. That is, the problem, it seems that Table 2.18 repeats 2.15 BO, corresponding, the BO and VO corresponding to T-TITEMACTTEACHER are not created.
6. Can you different tables correspond to the same BO, such as Table 2.12 and Table 2.14?
7. There is a conflict in the write code and database manual, such as TPITEMMETHODVO in TPITEMMETHODVO in Table 2.11, has a newly added ItemType, whether it is modified (I have added it in the code).
8. Who is the TPITEMIOBJECTVO corresponding to Table 2.9? Handbook or code?
9. In the Database.xml file, there is often one
