About JdbcMap

Provides mapping between JDBC ResultSets and Java objects.
The basic principles of VrameWork JdbcMap are:

• Simple mapping between JDBC ResultSets and objects
• The mapping information and SQL statements are defined in simple text files (the "mapping files")
• Mapping files are - if wanted - generated on the fly automatically (based on reflection and simple annotations): The generated files contain DDL and CRUD operations: Create tables and views (for class hierarchies), query, insert, update and delete objects.
  
  This is an excerpt from a sample mapping file:

  [select]
  type=read
  sql0=Select Select Customer.firstName, \
    Customer.lastName, \
    Customer.id, \
    Customer.dateOfBirth, \
    Customer.customerAdvisor_id, \
    Customer.customerAdvisor_classId, \
    Customer.classId\
  From View_ovmws_Customer as Customer
  fields0=_firstName|_lastName|_id|_dateOfBirth|_customerAdvisor._id|_customerAdvisor.classId|classId

  This is an outer join excerpt from a sample mapping file:
  

  [Outer_customerAdvisor]
  type=read
  outerJoinFields=_customerAdvisor
  sql0=Select Customer.firstName, \
    Customer.lastName, \
    Customer.id, \
    Customer.dateOfBirth, \
    Customer.customerAdvisor_id, \
    Customer.customerAdvisor_classId, \
    Customer.classId, \
    CustomerAdvisor0.firstName, \
    CustomerAdvisor0.lastName,   CustomerAdvisor0.id, \
    CustomerAdvisor0.phoneExtension, \
    CustomerAdvisor0.classId\ From View_ovmws_Customer as Customer Left Outer Join ViewSubclasses_ovmws_CustomerAdvisor as CustomerAdvisor0\
  On Customer.customerAdvisor_id = CustomerAdvisor0.id and Customer.customerAdvisor_classId = CustomerAdvisor0.classId
  fields0=_firstName|_lastName|_id|_dateOfBirth|_customerAdvisor._id|_customerAdvisor.classId|classId|_customerAdvisor._firstName|_customerAdvisor._lastName|_customerAdvisor._id|_customerAdvisor._phoneExtension|_customerAdvisor.classId

• The translation process between rows and objects is compiled. This is an important advantage in case of a data driven application which has to translate billions of rows to objects. Most O/R mappers have to rely on reflection to translate rows to objects and vv. JdcbMap does not because it creates and compiles so called "IRowTranslator"s at runtime.
• It provides generic classes for executing the SQLs in the mapping files and resolving class hierarchies.
  Sample:
  

  IClassRegistry classRegistry = JdbcMap.getClassRegistry();
  DataSource dataSource = MyAppConf.getDataSource();
  GenericDao<Customer> customerDao =
  new GenericDao<Customer>(Customer.class, classRegistry, "APP", dataSource);
  customerDao.createTablesAndViews();
  Customer = new Customer("First Name", "Last Name");
  // Inserts into the customer table and tables of base classes
  customerDao.insert(customer);
  List<Customer> customers = customerDao.selectAll();

• JdbcMap generates outer joins for efficient loading of lists of objects and referenced objects and thereby avoids the N+1 query problem.
• JdbcMap loads 1:n relationships very efficiently by setting the backlink on the "n" side is set during the compiled row translation process. This means: No reflection based setting of the backlink on the "n" side, no iterating over all loaded objects just to set the backlink.
• JdbcMap loads polymorphic lists and relationships efficiently. For example, if Customer has a reference to CustomerAdvisor (= a property of this type): At runtime, the concrete customer advisor can be any subclass of CustomerAdvisor.
• JdbcMap is pluggable: There are default implementations for all interfaces but you can inject your own implementations.

A more detailed description can be found in the JavaDoc and in the JdbcMap sample application.