Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Relational persistence: Most Java database programmers rely on the proven JDBC API. Why does SAP promote the newer standard, SQLJ?

0
Posted

Relational persistence: Most Java database programmers rely on the proven JDBC API. Why does SAP promote the newer standard, SQLJ?

0

We highly appreciate and support the JDBC-based application components! However, as we have learned over years, static SQL checks significantly improve the system reliability and maintainability and enormously speed the whole development process, first of all the testing phase. The SQLJ API even provides the static checks for your SQL statements. If you save your SQLJ source file, the SQLJ Checker immediately checks firstly the SQL syntax and secondly the accordance of the embedded names and types of database objects (tables, columns, and indexes) with the definitions in the database catalog. Try mixing SQLJ and JDBC: With SAP Web AS, you can convert the SQLJ connection context to the JDBC connection, and vice versa, in a straightforward manner. The same holds for JDBC result sets and SQLJ iterators. You can run SQLJ- and JDBC-based code even in the same database transaction. Both Open SQL/SQLJ and Open SQL/JDBC support the identical portable SQL set.

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.