public class _FrontBasePlugIn extends JDBCPlugIn
Modifier and Type | Class and Description |
---|---|
static class |
_FrontBasePlugIn.FrontbaseExpression |
static class |
_FrontBasePlugIn.FrontbaseSynchronizationFactory |
JDBCPlugIn.LobEntry
_adaptor, _expressionClass, _expressionFactory, _pkTableName, _subprotocolRegistry, _syncFactory, DefaultPlugInClassName, DefaultPlugInSuffix
Constructor and Description |
---|
_FrontBasePlugIn(JDBCAdaptor jdbcadaptor) |
Modifier and Type | Method and Description |
---|---|
boolean |
canDescribeStoredProcedure(String s) |
Properties |
connectionPropertiesForConnectionDictionary(NSDictionary connectionDictionary) |
EOSynchronizationFactory |
createSynchronizationFactory() |
String |
databaseProductName() |
String |
defaultDriverName() |
Class<? extends JDBCExpression> |
defaultExpressionClass() |
Object |
fetchBLOB(ResultSet resultset,
int i,
EOAttribute attribute,
boolean flag) |
Object |
fetchCLOB(ResultSet resultset,
int i,
EOAttribute attribute,
boolean flag) |
static String |
getPlugInVersion() |
NSDictionary<String,Object> |
jdbcInfo()
This is usually extracted from the the database using JDBC, but this is really inconvenient for users who are
trying to generate SQL at some.
|
String |
name()
WebObjects 5.4's version of JDBCAdaptor will use this in order to assemble the name of the prototype to use when
it loads models.
|
NSArray<NSDictionary<String,Object>> |
newPrimaryKeys(int numberOfKeys,
EOEntity eoentity,
JDBCChannel jdbcchannel) |
protected static String |
notNullConstraintName(EOAttribute attribute) |
protected static String |
notNullConstraintName(String tableName,
String columnName) |
protected static String |
quoteTableName(String s) |
String |
schemaNameForEntity(EOEntity eoentity) |
protected boolean |
shouldUseBundledJdbcInfo()
This method returns true if the connection URL for the database has a special flag on it which indicates to the
system that the jdbcInfo which has been bundled into the plugin is acceptable to use in place of actually going
to the database and getting it.
|
String |
storedProcedureSchemaPattern() |
void |
updateLOBs(JDBCChannel channel,
JDBCExpression expression,
NSDictionary<String,Object> row,
EOEntity entity) |
String |
wildcardPatternForSchema() |
_attributeForPath, _couldIgnoreException, _relationshipForPath, _takeValueForKeyPath, adaptor, assignTypeForAttribute, connectionURL, createAttributeForRow, createExpressionFactory, createSchemaSynchronizationFactory, databaseInformation, expressionFactory, isDroppedConnectionException, isPseudoColumnName, jdbcTypeForUnknownExternalType, newPrimaryKeySelectString, plugInNameForURL, plugInValueForValue, primaryKeyLockString, primaryKeyTableCreateString, primaryKeyTableName, removePlugInNameForSubprotocol, schemaSynchronizationFactory, setPlugInNameForSubprotocol, sqlStatementForGettingProcedureNames, sqlStatementForGettingTableNames, sqlStatementForTableNamed, storedProcedureCatalogPattern, storedProcedureNamed, synchronizationFactory, tableTypes, wildcardPatternForAttributes, wildcardPatternForTables
public _FrontBasePlugIn(JDBCAdaptor jdbcadaptor)
public static String getPlugInVersion()
public boolean canDescribeStoredProcedure(String s)
canDescribeStoredProcedure
in class JDBCPlugIn
public EOSynchronizationFactory createSynchronizationFactory()
createSynchronizationFactory
in class JDBCPlugIn
public String defaultDriverName()
defaultDriverName
in class JDBCPlugIn
public String databaseProductName()
databaseProductName
in class JDBCPlugIn
public String name()
WebObjects 5.4's version of JDBCAdaptor will use this in order to assemble the name of the prototype to use when it loads models.
name
in class JDBCPlugIn
protected boolean shouldUseBundledJdbcInfo()
This method returns true if the connection URL for the database has a special flag on it which indicates to the system that the jdbcInfo which has been bundled into the plugin is acceptable to use in place of actually going to the database and getting it.
true
jdbcInfo which has been bundled into the plugin is acceptable to usepublic Class<? extends JDBCExpression> defaultExpressionClass()
defaultExpressionClass
in class JDBCPlugIn
public String wildcardPatternForSchema()
wildcardPatternForSchema
in class JDBCPlugIn
public String schemaNameForEntity(EOEntity eoentity)
schemaNameForEntity
in class JDBCPlugIn
public String storedProcedureSchemaPattern()
storedProcedureSchemaPattern
in class JDBCPlugIn
public Properties connectionPropertiesForConnectionDictionary(NSDictionary connectionDictionary)
connectionPropertiesForConnectionDictionary
in class JDBCPlugIn
public NSDictionary<String,Object> jdbcInfo()
This is usually extracted from the the database using JDBC, but this is really inconvenient for users who are trying to generate SQL at some. A specific version of the data has been written into the property list of the framework and this can be used as a hard-coded equivalent.
jdbcInfo
in class JDBCPlugIn
public void updateLOBs(JDBCChannel channel, JDBCExpression expression, NSDictionary<String,Object> row, EOEntity entity)
updateLOBs
in class JDBCPlugIn
public Object fetchBLOB(ResultSet resultset, int i, EOAttribute attribute, boolean flag) throws SQLException
fetchBLOB
in class JDBCPlugIn
SQLException
public Object fetchCLOB(ResultSet resultset, int i, EOAttribute attribute, boolean flag) throws SQLException
fetchCLOB
in class JDBCPlugIn
SQLException
public NSArray<NSDictionary<String,Object>> newPrimaryKeys(int numberOfKeys, EOEntity eoentity, JDBCChannel jdbcchannel)
newPrimaryKeys
in class JDBCPlugIn
protected static String notNullConstraintName(EOAttribute attribute)
protected static String notNullConstraintName(String tableName, String columnName)
Copyright © 2002 – 2024 Project Wonder.