com.aceql.jdbc.commons.metadata.ResultSetMetaDataPolicy Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of aceql-http-client-jdbc-driver Show documentation

The AceQL Java Client JDBC Driver allows to wrap the AceQL HTTP APIs and eliminates the tedious works of handling communications errors and parsing JSON results. Android and Java Desktop application developers can access remote SQL databases and/or SQL databases in the cloud by simply including standard JDBC calls in their code, just like they would for a local database.

The newest version!

/**
 *
 */
package com.aceql.jdbc.commons.metadata;

import com.aceql.jdbc.commons.AceQLConnection;

/**
 * Defines the policy for {@code ResultSetMetaData} access:
 * 
 * on: {@code ResulSetMetaData} will be always accessible, because
 * downloaded along with ResultSet for each {@code SELECT}. This will allow to use
 * {@code ResultSet#getMetaData()} calls, but {@code SELECT} calls will be a bit
 * slower.
 * off: {@code ResulSetMetaData} will always be null because not downloaded
 * along with {@code ResultSet} for each {@code SELECT} call. Thus, {@code SELECT} calls
 * will be faster.
 * 
 * 
 * Set the ResulSetMetaData Driver property to "on" or "off" to choose your
 * preferred behavior. Default value for a new {@link AceQLConnection} is
 * {@code ResultSetMetaDataPolicy.on}.
 * 

 * @since 6.0
 * @author Nicolas de Pomereu
 *
 */
public enum ResultSetMetaDataPolicy {

    /**
     * {@code ResulSetMetaData} will be always accessible, because downloaded along
     * with {@code ResultSet} on each {@code SELECT} call.
     */
    on,

    /**
     * {@code ResulSetMetaData} will always be null because not downloaded along
     * with {@code ResultSet} on each {@code SELECT} call.
     */
    off
}