I started to solve the problem of query problems in current data persistence. In order to solve the problem of inquiry in the persistence process, the initial solution is first determined. Define your own persistent class, define the properties of the lasting class with your own data type, and then implement a mechanism to make us a computer language such as Java to write a SQL statement to generate a query. The programmer defines the process of defining the query by using the frame design API, which is actually the process of translating the computer language into a SQL language. Since all persistent classes must inherit the persistent class defined from the framework, the attributes of the lasting class must be defined as the type defined by the framework, so the programmer is controlled by the programmer through the calculation of the base language such as the Java defined query. Therefore, it makes it possible to translate programmers to write computer languages to SQL statements. Moreover, the framework enables programmers to call the framework mapping mechanism before using the persistent class to load the persistent class to load database mapping information from the external configuration file, so that the persistent class is valid for solicito. Not imaged in some of the previous implementations in the program hard coded database structure information. This program is feasible on the current situation. Although there is still a simplified room in some aspects, in general, there is a plan for initially solving problems.
