Package org.sqlproc.engine

The public part of the SQL Processor implementation.

See:
Description

Interface Summary

SqlFeature	Optional features, which can be activated in the process of SQL Processor initialization.
SqlMonitor	The vehicle interface definition, which can be used to monitor the duration of all SQL queries execution.
SqlMonitor.Runner	This interface is implemented in SqlQueryEngine and SqlCrudEngine main public methods.
SqlMonitorFactory	The factory definition, which can be used to construct SqlMonitor.

Class Summary

SqlCrudEngine	The primary SQL Processor class for the META SQL CRUD statement execution.
SqlEngine	Common ancestor for SqlQueryEngine and SqlCrudEngine.
SqlEngineLoader	Helper class for the parsing of META SQL statements and Mapping rules located in properties file.
SqlOrder	The list of ordering directives for the SQL Processor queries execution.
SqlPropertiesLoader	Helper class for the properties file loading.
SqlQueryEngine	The primary SQL Processor class for the META SQL query execution.

Enum Summary

SqlOrder.Order

The enumeration for the ordering directives.

Exception Summary

SqlEngineException

General exception class for the SQL Processor parser.

Package org.sqlproc.engine Description

The public part of the SQL Processor implementation. The most important classes are SqlQueryEngine and SqlCrudEngine. There are also some helper classes and basic interfaces.

SQL Processor is Data Driven Query Engine. It's able to dynamically generate ANSI SQL query or statement based on search data provided by an end user or an application. This is done in the runtime, without any plumbing code required.

In other words - SQL Processor has 3 basic inputs:

• A META SQL query or statement. META SQL is an ANSI SQL extension based on ANTLR grammar. For example the META SQL query is
  select p.ID id, p.NAME name from PERSON p {= where {& p.id=:id} {& UPPER(name)=:+p.name}}
• Input values provided by an end user. These data are collected in a search form, a standard POJO object, which can be created in a presentation layer of a web application.
• A result class definition, which is used to carry output data from a SQL query execution. This class is a standard POJO object, instances of which are created in the SQL Processor without any plumbing code. It can work as a transport object from a persistence to a presentation layer of a web application.

Next, the SQL Processor has one output - the list of result class instances.

For the META SQL query described above the generated ANSI SQL can be

• select p.ID id, p.NAME name from PERSON p in the case there are no values in a search form or this search form is null.
• select p.ID id, p.NAME name from PERSON p where id=? in the case there's a not null value for id attribute in a search form.

In the process of data collection from a search form it's used Reflection API. The same API is used in the process of seeding instances of result class with the SQL query execution output.

The package org.sqlproc.engine.impl contains non public part of the SQL Processor implementation. The implementation of this part can be changed any time to improve the SQL Processor capabilities.

For more info please see the Reference Guide or tutorials.

Author:

Vladimir Hudec