pubic class Employee { PRivate int employeeId; private String firstName; private String lastName; public int getEmployeeId() { return employeeId; } public setEmployeeId(int employeeId) { this.employeeId = employeeId; } public String getFirstName() { return firstName; } public setFirstName(String firstName) { this.firstName = firstName; } public String getLastName() { return lastName; } public setLastName(String lastName) { this.lastName = lastName; } } interface EmployeeQueries extends BaseQuery { @Select (sql="SELECT employeeId， firstName， lastName FROM employee") DataSet<Employee> getAllEmployees (); @Update (sql="delete from employee") int deleteAllEmployees (); } Connection con = ... EmployeeQueries empQueries = con.createQueryObject (EmployeeQueries.class); DataSet<Employee> empData = empQueries.getAllEmployees (); 二、 改進異常處理能力
在JDBC API 4.0以前的版本中，異常處理功能極其有限。對于所有類型的錯誤都會籠統(tǒng)地拋出一個SQLException異常-根本不存在異常的具體分類，且沒有相應的層次定義。所以這時，你唯一能夠得到一些有意義的信息的辦法是檢索和分析SQLState值。另一方面，SQLState值及其相應的含義會因不同的數(shù)據(jù)源而有所改變；因此，要想追蹤到問題的"根部"并且有效地處理異常是一件非常乏味的任務。
