The different between JPA query statement and native SQL

For JPA, it supports named parameter, such as :parameter1, :parameter2.
For native SQL query, it supports positional parameter, such as ?1, ?2.

留言

張貼留言

這個網誌中的熱門文章

Using NPM behind proxy

Config NPM behind proxy by config  and proxy or https-proxy : npm config set proxy http://proxy.company.com:8080 npm config set https-proxy http://proxy.company.com:8080 If you want to specify the credential, they can passed by the following URL syntax: http:// username:password @proxy.company.com:8080
閱讀完整內容

10 Tips for Proper Application Logging

圖片
Reference: https://www.javacodegeeks.com/2011/01/10-tips-proper-application-logging.html   Our latest   JCP partner ,   Tomasz Nurkiewicz , has submitted a number of posts describing the basic principles of proper application   logging . I found them quite interesting, thus I decided to aggregate them in a more compact format and present them to you. So, here are his suggestions for clean and helpful logs:(NOTE: The original posts have been slightly edited to improve readability) 1) Use the appropriate tools for the job Many programmers seem to forget how important is logging an application’s behavior and its current activity. When somebody puts: 1 log.info( "Happy and carefree logging" ); happily somewhere in the code, he probably doesn’t realize the importance of application logs during maintenance, tuning and failure identification. Underestimating the value of good logs is a terrible mistake. In my opinion, SLF4J is the best logging API availab...
閱讀完整內容

Logging Best Practices

Logging in Java Reference: https://wiki.opendaylight.org/view/BestPractices/Logging_Best_Practices Java provides a diverse set of logging APIs and implementations. OpenDaylight has selected   SLF4J API , with the implementation being provided by the Karaf container. The primary reasons for this decision are: proper split between API and implementation, allowing us to change the implementation without impacting code ability to provide legacy APIs (JUL, JCL, etc.) for third-party code Message levels SLF4J defines five levels of logging messages, ranging from   TRACE   to   ERROR . The guidelines for their use are very vague and in the grand UNIX tradition mix severity of the message with its granularity. The following summary defines the basic rules on when to use a specific level, who the target audience is and how any message of the specified level will be interpreted. Note that all events with level   INFO or higher present an API-like contract...
閱讀完整內容