[teiid-issues] [JBoss JIRA] (TEIID-2610) pg protocol issues

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Wed Jul 31 18:57:26 EDT 2013


    [ https://issues.jboss.org/browse/TEIID-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794381#comment-12794381 ] 

Steven Hawkins edited comment on TEIID-2610 at 7/31/13 6:56 PM:
----------------------------------------------------------------

Other issues include:
- multiple portals can be opened against a single prepared statement at a time - which requires allowing the statement result to not be implicitly closed in our StatementImpl.
- possibly the wrong portal is being closed when the statement is closed
- max rows is being read incorrectly for the execute message and is not implemented correctly as max rows (it needs to be a forward only cursoring mechanism rather than just a limit)
- if multiple binds are issued against a single statement before an execute, the parameters are not associated correctly

Minor issues:
- the unnamed constant should be the empty string to not conflict with the actual name "UNNAMED"
- only the bind of the unnamed portal should remove the previous unnamed
- it's an error to reuse an explicitly named portal/statement if one already exists
- it's not an error to close a non-existent portal

We also need to consider adding transaction awareness so that portals are cleaned up as expected.
                
      was (Author: shawkins):
    Other issues include:
- multiple portals can be opened against a single prepared statement at a time - which requires allowing the statement result to not be implicitly closed in our StatementImpl.
- possibly the wrong portal is being closed when the statement is closed

Minor issues:
- the unnamed constant should be the empty string to not conflict with the actual name "UNNAMED"
- only the bind of the unnamed portal should remove the previous unnamed
- it's an error to reuse an explicitly named portal/statement if one already exists
- it's not an error to close a non-existent portal

We also need to consider adding transaction awareness so that portals are cleaned up as expected.
                  
> pg protocol issues
> ------------------
>
>                 Key: TEIID-2610
>                 URL: https://issues.jboss.org/browse/TEIID-2610
>             Project: Teiid
>          Issue Type: Bug
>          Components: ODBC
>    Affects Versions: 7.7
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 8.4.1, 8.5
>
>
> The primary issue is that closing a portal is also closing the prepared plan, which is causing a protocol error.

--
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


More information about the teiid-issues mailing list