[teiid-issues] [JBoss JIRA] Commented: (TEIID-1700) Move odbc cursor logic to engine

[ https://issues.jboss.org/browse/TEIID-1700?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1700: --------------------------------------- I'll looking at this as a candidate for 7.6. The main advantage of having a cursor type/logic in the engine would be for passing to procedures (and possibly functions). With generalization in/out and out could be handled as well and would no longer necessitate having only one result set. Without additional designer support though the workaround would be to pass cursors using the object type and then using a cast. One possible issue is that the PG logic has a special case for cursor execution through a portal. I'm not sure if that would remain valid if the engine were handling DECLARE CURSOR/MOVE/FETCH/CLOSE. Ramesh is there still a regular portal created in this case? JDBC access with a few enhancements (backwards fetch, better absolute positioning) still wouldn't directly need a cursor concept. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira