[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1131: --------------------------------------- The metadata processor logic at least for pg/oracle can be made to perform the sequence as function import automatically. For example the following could augment the createMetadataProcessor call in the OracleExecutionFactory: {code} @Override protected Table addTable(MetadataFactory metadataFactory, String tableCatalog, String tableSchema, String tableName, String remarks, String fullName, ResultSet tables) throws SQLException { String tableType = tables.getString(4); if ("SEQUENCE".equals(tableType)) { //$NON-NLS-1$ FunctionMethod method = metadataFactory.addFunction((useFullSchemaName?fullName:tableName) + "_nextval", TypeFacility.RUNTIME_NAMES.INTEGER); //$NON-NLS-1$ method.setProperty(SQLConversionVisitor.TEIID_NATIVE_QUERY, getFullyQualifiedName(tableCatalog, tableSchema, tableName, true) + ".nextval"); //$NON-NLS-1$ method = metadataFactory.addFunction((useFullSchemaName?fullName:tableName) + "_currval", TypeFacility.RUNTIME_NAMES.INTEGER); //$NON-NLS-1$ method.setProperty(SQLConversionVisitor.TEIID_NATIVE_QUERY, getFullyQualifiedName(tableCatalog, tableSchema, tableName, true) + ".currval"); //$NON-NLS-1$ return null; } return super.addTable(metadataFactory, tableCatalog, tableSchema, tableName, remarks, fullName, tables); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira