[ https://jira.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin.s... ] Steve Hawkins commented on TEIID-1131: -------------------------------------- Added a note to the 7.0 docs. Will look at expanding support initially in 7.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated TEIID-1131: ---------------------------------- Fix Version/s: 7.3 (was: 7.2) pushing to 7.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1131: --------------------------------------- in looking at sequence options, the clearest choice is to only support next value. curval is problematic since it is generally session dependent and we may not be the same source connection. This is also somewhat consistent with sql 2006, which only has "NEXT VALUE FOR <sequence>" - whatever support is added, it would be good to add support for the sequence generator in hibernate, which would suggest that it needs to be a standalone retriveable value and not just used as a default (currently supported in a workaround fashion only for oracle) - currently with Hibernate the workaround is to use the native support - which would default to the table generator or support for the GUIDGenerator was just added via the uuid function. Possible design choices are: 1. proper metadata support - won't work in designer until a metamodel update - ideally needs import support 2. function approach, e.g. nextval('x') - needs a notion of what are valid sequence names In any case there are significant calling differences among sources: - h2 nextval([<schema>],<sequencename>) - postgres nextval(<sequencename>) - hsql NEXT VALUE FOR <sequencename> - d2/oracle <sequencename>.nextval etc. which may need slightly modified sql to select a standalone value. We can use the Hibernate Dialects to determine what should be called. On a related note, we should also add enhancement to support generated keys. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1131: ---------------------------------- Fix Version/s: 8.1 (was: 8.0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1131: --------------------------------------- For oracle inserts if a table has an autoincrement column with a name in source of :SEQUENCE=sequencename.val, then we'll use the sequence value in the insert submitted to Oracle if no value has been set for that column. For any other sequence usage you'd have to model the sequence as a UDF or procedure depending on how you need to call it and whether you need the value to be inlined or obtained from a separate statement. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1131: ---------------------------------- Fix Version/s: 8.2 (was: 8.1) Pushing to 8.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira