[ https://issues.jboss.org/browse/TEIID-5074?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5074: --------------------------------------- Actually the dialect change that was just committed is incorrect. The call needs to be nested in parens to be a valid scalar subquery. Taking a step back, if we could just use a function you'd ideally use a convention like: {code} @Override public String getSequenceNextValString(String sequenceName) { return "select " + getSelectSequenceNextValString( sequenceName ); } @Override public String getSelectSequenceNextValString(String sequenceName) { return sequenceName + "_nextval()"; } {code} Such that with an import option turned on for oracle/postgresql/etc., we'd automatically create the functions sequence_nextval and sequence_curval. Note that using the _nextval convention matches the other places in our docs where we mention sequence support. A small issue is that in the SequenceGenerator annotation it would be best to have the name fully qualified. -- This message was sent by Atlassian JIRA (v7.2.3#72005)