Skip to main content

Getting warnings from JDBC Connection

Image
By
Sometimes it is a wise decision to retrieve the first warning reported by calls on this Connection object. This can be done using getWarnings() method. The code sample below shows how to print all the warnings with their sates and messages.


Class.forName( "sun.jdbc.odbc.JdbcOdbcDriver" ) ;
Connection conn = DriverManager.getConnection( "jdbc:odbc:Database" ) ;

// Print all warnings
for( SQLWarning warn = conn.getWarnings(); warn != null; warn = warn.getNextWarning() )
{
System.out.println( "SQL Warning:" ) ;
System.out.println( "State : " + warn.getSQLState() ) ;
System.out.println( "Message: " + warn.getMessage() ) ;
System.out.println( "Error : " + warn.getErrorCode() ) ;
}
Labels:

Comments

Post a Comment

Popular posts from this blog

svn credentials caching

By
SVN client has a built-in system for caching authentication credentials on disk. It saves the credentials in the user's private runtime configuration area ~/.subversion/auth/ (Unix-like systems) %APPDATA%/Subversion/auth/ (Windows) If you dont want to catch the credeitials for a commit, use --no-auth-cache. $ svn commit --no-auth-cache Here we are telling the svn client that dont cach authentication credentials. You can disable credential caching permanently by editing your runtime config file (located next to the auth/ directory). Set store-auth-creds to no. [auth] store-auth-creds = no
Post a Comment
Read more

log4j - use logger instead of category

By
Do not use 'category'. In log4j 1.2, the Category class has marked as being deprecated and has been replaced by the Logger class. I am using log4j-1.2.14.jar and category didn't work for me. Example: <logger name="com.test.pkg1"><level value="INFO"/></logger> <logger name="com.test.pkg2"><level value="INFO"/></logger> Was: <category name="com.test.pkg1"><priority value="INFO"/></category> <category name="com.test.pkg2"><priority value="INFO"/></category>
Post a Comment
Read more

Java Data Objects

By
JDO has nothing to do with where methods are executed. JDO simply specifies how the fields of a petent object should be managed in-memory, being transparently stored to and retrieved from an underlying datastore. With JDO, methods are invoked on persistent object by an application, as per any regular in-memory Java object. JDO has many implementations. Visit the following link to know about the available implementations. http://db.apache.org/jdo/impls.html
Post a Comment
Read more