What are native questions?

Native questions are queries expressed through the structured language language (SQL) and are brief and type methods safe for C ++ and Java queries. The use of native queries is beneficial in using specific functions in databases, including hints of questions and certain database specific functions. They are also useful in providing net migration paths directly from applications using SQL or Java database (JDBC ™). Native questions are used to provide results consisting of scalar values, entities or both. These types of queries support the use of native SQL in the target database. Questions of this kind are used in database of objects where the persistence of the object is a common task for programmers and a common feature of the database. However, in programs that are object -oriented in programs because of their expressions, they appear in programs that are simple in non -oriented -oriented and object graphs containing scattered chains. LZ questionse to write without an API or adapted inquiry language. In addition, the integrated development environment (IDE) is able to help reduce typing. Native questions would then be in a safe type across and available to them. Finally, the questions may be triggered, tested and prototyped against a simple memory collection without the rear end of the database.

Questions and their accompanying SQL do not necessarily have to be transferred in other databases. After the return of many entities by a particular native query, these same entities should be specified and mapped to make columns results in SQL commands in the Metadat software program. As a result, Jee can be used to map the results of JDBC persistent during the expected objects. The use of the name parameter is never defined for these types of queries, and portable applications can only use position parameters for native SQL queries. SPO supportJů is limited to the relationships of individual values.

For the use of native queries, the programmer must describe a set of SQL results. The description of the results set helps the program, such as the EntityManager map column on the entities. Scalar results can also be defined and mixed with other entity results, resulting in the return of the alias column. Once the results are described, native questions can be done.