Examples of SQLStatement

• com.alibaba.druid.sql.ast.SQLStatement
• com.odiago.flumebase.parser.SQLStatement
  Abstract base class for statements in the SQL statement AST
• liquibase.statement.SqlStatement
  The SqlStatement classes correspond to (roughly) a single SQL statement. SqlStatement instances are created by Change classes, and by Liquibase itself as the primary database-independent abstraction of statments to execute against a database.

  A single SqlStatement may yield multiple SQL commands, and may yield a different number of SQL commands depending on the database. If a particular statement. The SqlStatement implementations do not actually generate SQL strings, that is left to the SqlGenerator implementations. Instead, the purpose of the SqlStatement implementation is to hold the metadata required to generate the correct SQL for a particular database at a later time. @see liquibase.change.Change @see liquibase.sqlgenerator.SqlGenerator @see liquibase.sqlgenerator.SqlGeneratorFactory

• mondrian.rolap.SqlStatement
  ndrian-release/3.2/src/main/mondrian/rolap/SqlStatement.java#5 $ @author jhyde @since 2.3
• nexj.core.meta.persistence.sql.SQLStatement
  SQL statement used in the SQLExec step.
• org.apache.beehive.controls.system.jdbc.parser.SqlStatement
  Represents a fully parsed SQL statement. SqlStatements can be used to generated a java.sql.PreparedStatement.
• org.apache.oozie.util.db.SqlStatement
  The SqlStatement is used to generate SQL Statements. Prepare the generated Statements and also to parse the resultSets
• org.datanucleus.store.rdbms.sql.SQLStatement
  Class providing an API for generating SQL statements. Caller should create the SQLStatement object and (optionally) call setClassLoaderResolver() to set any class loading restriction. Then the caller builds up the statement using the various methods, and accesses the SQL statement using getStatement(). Generated statement is of the form :-

   SELECT {expr}, {expr}, ... FROM {tblExpr} [joinInfo {tblExpr} ON ...] ... WHERE {boolExpr} [AND|OR] {boolExpr} ... GROUP BY {expr}, {expr} HAVING {boolExpr} ORDER BY {expr} [ASC|DESC], {expr} [ASC|DESC], ... 

  and also supports UNIONs between SQLStatements, and having sub-queries of other SQLStatements. Alternatively, for an UPDATE,

   UPDATE {tbl} SET {expr}={val}, {expr}={val}, ... WHERE {boolExpr} [AND|OR] {boolExpr} ... 

  The generated SQL is cached. Any use of a mutating method, changing the composition of the statement will clear the cached SQL, and it will be regenerated when

  getStatement

  is called next.

  Table Groups

  When tables are registered in the statement they are split into "table groups". A table group is, in simple terms, an object in the query. If a table has a super-table and a field of the object is selected that is in the super-table then the super-table is added to the table group. If there is a join to a related object then the table of this object will be put in a new table group. So the same datastore table can appear multiple times in the statement, each time for a different object.

  Table Aliases

  All methods that cause a new SQLTable to be created also allow specification of the table alias in the statement. Where the alias is not provided then we use a table "namer" (definable on the plugin-point "org.datanucleus.store.rdbms.sql_tablenamer"). The table namer can define names simply based on the table number, or based on table group and the number of tables in the group etc etc. To select a particular table "namer", set the extension "datanucleus.sqlTableNamingStrategy" to the key of the namer plugin. The default is "alpha-scheme" which bases table names on the group and number in that group.
• org.ofbiz.sql.SQLStatement
• org.sonar.server.db.migrations.SqlStatement
• org.sql.generation.api.grammar.common.SQLStatement
• org.xmlBlaster.contrib.replication.SqlStatement
  SqlStatement @author Michele Laghi

Examples of org.xmlBlaster.contrib.replication.SqlStatement