Essential ADO.NET

9.11. SQL/J Part 0 and Typed DataSets

JDBC ResultSets, like the ADO.NET DataReader and all other dynamic SQL APIs equivalents, will produce runtime errors if the specified column name or column number does not exist at runtime. This problem is discussed in Chapter 7 in conjunction with the ADO.NET strongly typed DataSet class, a subclass of DataSet, which provides compile-time checking based on database metadata.

Although JDBC does not have the concept of strongly typed subclasses, an addition to the SQL-99 spec known as “SQL/J part 0” provides equivalent functionality by supporting embedded SQL, that is, escaped SQL statements embedded within program code. The embedded SQL is processed by a preprocessor, so SQL clauses can contain actual Java ...