openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1054) Large result sets do not work with MySQL
Date Thu, 07 May 2009 13:22:30 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Donald Woods updated OPENJPA-1054:
----------------------------------

    Patch Info: [Patch Available]

> Large result sets do not work with MySQL
> ----------------------------------------
>
>                 Key: OPENJPA-1054
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1054
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>            Reporter: Rick Curtis
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: OPENJPA-1054.patch
>
>
> Large result sets do not work as documented. I did some googling around [1] and found
a number of posts talking about how setFetchSize on the JDBC driver isn't being honored, some
dating back as far as 2002. The MySQL docs [2] state "When using versions of the JDBC driver
earlier than 3.2.1, and connected to server versions earlier than 5.0.3, the setFetchSize()
method has no effect, other than to toggle result set streaming as described above.". The
doc outlines some additional instructions on how to create a statement that is going to allow
a streaming result set. 
> I spoke with Fey and she provided me with a patch that will allow us to use LRS with
some limitations. I'm in the process of updating the docs and adding tests for the patch that
Fey provided.
> [1] Google "mysql jdbc setFetchSize"
> [2]http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-implementation-notes.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message