| org.geotools.data.jdbc.JDBCDataStore
 org.geotools.data.geometryless.JDBCDataStore
All known Subclasses: org.geotools.data.geometryless.BBOXDataStore, org.geotools.data.geometryless.LocationsXYDataStore,
| DEFAULT_NAMESPACE | | public static String DEFAULT_NAMESPACE(Code) | | DEFAULT_NAMESPACE field
|
| buildAttributeType | | protected AttributeType buildAttributeType(ResultSet rs) throws IOException(Code) | | Constructs an AttributeType from a row in a ResultSet. The ResultSet
contains the information retrieved by a call to getColumns() on the
DatabaseMetaData object. This information can be used to construct an
Attribute Type.
In addition to standard SQL types, this method identifies MySQL 4.1's
geometric datatypes and creates attribute types accordingly. This happens
when the datatype, identified by column 5 of the ResultSet parameter, is
equal to java.sql.Types.OTHER. If a Types.OTHER ends up not being
geometric, this method simply calls the parent class's buildAttributeType
method to do something with it.
Note: Overriding methods must never move the current row pointer in the
result set.
Parameters:
rs - The ResultSet containing the result of aDatabaseMetaData.getColumns call. The AttributeType built from the ResultSet.
throws:
SQLException - If an error occurs processing the ResultSet.
throws:
DataSourceException - Provided for overriding classes to wrap exceptions caused byother operations they may perform to determine additionaltypes. This will only be thrown by the default implementationif a type is present that is not present in theTYPE_MAPPINGS. |
| getFeatureTypeHandler | | protected FeatureTypeHandler getFeatureTypeHandler(JDBCDataStoreConfig config) throws IOException(Code) | | Overrides JDBC1DataStore.getFeatureTypeHandler to return
an in-process view aware one, a
Parameters:
config - a that maintains aregistry of user defined SQL queries exposed as read-onlyFeatureTypes |
| getFeatureWriter | | public FeatureWriter getFeatureWriter(String typeName) throws IOException(Code) | | Utility method for getting a FeatureWriter for modifying existing
features, using no feature filtering and auto-committing. Not used for
adding new features.
Parameters:
typeName - the feature type name (the table name) a FeatureWriter for modifying existing features
throws:
IOException - if the database cannot be properly accessed |
| getFeatureWriterAppend | | public FeatureWriter getFeatureWriterAppend(String typeName) throws IOException(Code) | | Utility method for getting a FeatureWriter for adding new features, using
auto-committing. Not used for modifying existing features.
Parameters:
typeName - the feature type name (the table name) a FeatureWriter for adding new features
throws:
IOException - if the database cannot be properly accessed |
| getSqlBuilder | | public SQLBuilder getSqlBuilder(String typeName) throws IOException(Code) | | Returns a SQLBuilder for the requested FeatureType.
If the requested FeatureType corresponds to an in-process view (a view
specified through
, the
returned SQLBuilder takes care of it.
|
| registerView | | public void registerView(String typeName, SelectBody select) throws IOException(Code) | | I'm adding this method right now just to get the class compiling. By now
it just delegates to the old
JDBCDataStore.registerView(String,String) with
the toString() value of the select body. In the short
term, the delegation shuold be inversed so the datastore uses the object
model representing the query instead of parsing the string query "by
hand".
|
| registerView | | public void registerView(String typeName, String sqlQuery) throws IOException(Code) | | Creates an in-process data view against one or more actual FeatureTypes
of this DataStore, which will be advertised as typeName
Parameters:
typeName - the name of the view's FeatureType.
Parameters:
sqlQuery - a full SQL query which will act as the view definition.
throws:
IOException -
throws:
IllegalArgumentException - if typeName already exists as one of thisdatastore's feature types, regardless of type name case. |
|
|