[ https://issues.jboss.org/browse/TEIID-5074?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5074: ------------------------------------- If source database like H2 defines a SEQUENCE like {code} CREATE SEQUENCE IF NOT EXISTS customer_seq START WITH 200 INCREMENT BY 1; {code} Then when you define a SEQUENCE based Entity in your JPA as {code} public class Customer { @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "customer_generator") @SequenceGenerator(name="customer_generator", sequenceName = "customer_seq") @Id Long id; } {code} Then TeiidDialect expects a procedure defined in one of the visible virtual schemas as {code} CREATE VIRTUAL PROCEDURE customer_seq(OUT "return" long RESULT) AS BEGIN -- Your code to retrieve the sequence from Oracle. END; {code} The query that will be executed from the JPA layer will be like following to fetch teh sequence {code} select __x.return from (call customer_seq()) as __x {code} In Spring Boot implementation for auto-generation of code, sequence MUST be qualified with "schema" like "mydb.customer_seq" and then a following metadata is generated {code} -- in the source model "mydb" following will be generated CREATE FOREIGN FUNCTION customer_seq(OUT "return" long RESULT) OPTIONS ("teiid_rel:native-query" 'SELECT NEXTVAL(''customer_seq'');'); -- in the view model, the following will be generated CREATE VIRTUAL PROCEDURE customer_seq(OUT "return" long RESULT) AS BEGIN SELECT mydb.customer_seq(); END; {code} This model gives the flexibility to the user how they would like to implement the SEQUENCE through a virtual procedure. -- This message was sent by Atlassian JIRA (v7.2.3#72005)