Oracle tables associated query more suitable for persistence layer framework?-CodePudding

Project the situation is:
Most of the table 1, the use of oracle database, field more than 30;
2, need more league table query, and returns the multiple tables and query result set.

Excuse me each great god what advice can convenient maintenance of the persistence layer development?

CodePudding user response:

Are not mybatis now

CodePudding user response:

refer to the original poster; wang cui response:

project the situation is:
Most of the table 1, the use of oracle database, field more than 30;
2, need more league table query, and returns the multiple tables and query result set.

Excuse me each great god what advice can convenient maintenance of the persistence layer development?

Feel with what frameworks are not appropriate, we encounter this kind of all don't write Java code, configuration interface directly output data docking front end,
I take a look at the following introduction, if need to private chat I

 
Interface configuration compared to the traditional handwritten background (JAVA/c #/PHP) code, what are the advantages? 
Answer: 1, to save time, write the code out the speed of the interface cannot be compared with interface configuration 
2, save resources, such as the human cost, material cost, financial costs, this is not much said, as soon as the account is clear 
3, fewer bugs, code BUG with too much, the more interface configuration without having to write code, BUG is almost zero, unless there is something wrong with the SQL stored procedure or internal 
4, the release of more efficient, traditional version contains tedious pack/upload/cover/restart four steps, interface configuration to online development, the same environment without hair version, just click the button to different environment data export and import, the process of production and test version can still send each other 
5, a lower threshold, handwritten code that developers must master a computer language, an interface configuration you just need to be familiar with the database knowledge 
6, maintenance more convenient, if demand change, the traditional way need to change the code to test version, just need to change the SQL online interface configuration 
7, test more worry, traditional interface to write a unit test or with the aid of tools to test, testing interface, interface configuration parameters, just click on the button, it can test 
8, more relaxed, docking interface to write is for third-party docking, the traditional way of handwritten interface documentation, used to each person is different, the document is multifarious and docking way, interface configuration is automatically generated interface documentation, unified docking way, also provide docking example 
9, the data more secure, docking authentication with the method of signature certification, with similar WeChat payment interface, compared to a token, a higher security level 
10, transition easier, new colleague to take over the SQL is much simple than take code

CodePudding user response:

Mybatis: small, convenient, efficient, simple, direct, semi-automatic

Hibernate: powerful, convenient, efficient, complex, indirect, fully automated

Recommend mybatis using simple point, handwritten SQL, more flexible