OpenJPA
  1. OpenJPA
  2. OPENJPA-1863

update HSQL dictionary for HSQLDB 2.0

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.0, 2.2.0
    • Component/s: jdbc, sql
    • Labels:
      None
    • Patch Info:
      Patch Available

      Description

      "useGetObjectForBlobs" should be set to false for HSQLDB 2.0

        Activity

        Hide
        Georgi Naplatanov added a comment -

        The patch should fix this issue.

        Show
        Georgi Naplatanov added a comment - The patch should fix this issue.
        Hide
        Georgi Naplatanov added a comment -

        SVN patch

        Show
        Georgi Naplatanov added a comment - SVN patch
        Hide
        Milosz Tylenda added a comment -

        Georgi, thanks for the patch. I applied it to trunk with some modifications - when using schema creation, BLOB/CLOB attributes are mapped to BLOB/CLOB columns instead of VARBINARY/VARCHAR as it is with HSQLDB 1.8.

        There is some room for improvement still, e.g. there is an issue with setFirst/MaxResults.

        Show
        Milosz Tylenda added a comment - Georgi, thanks for the patch. I applied it to trunk with some modifications - when using schema creation, BLOB/CLOB attributes are mapped to BLOB/CLOB columns instead of VARBINARY/VARCHAR as it is with HSQLDB 1.8. There is some room for improvement still, e.g. there is an issue with setFirst/MaxResults.
        Hide
        Georgi Naplatanov added a comment -

        Hi Milosz.

        Thanks for your attention.

        setFirst/MaxResults is important feature. Where is the problem ? bug in HSQLDB 2.0 ?

        Show
        Georgi Naplatanov added a comment - Hi Milosz. Thanks for your attention. setFirst/MaxResults is important feature. Where is the problem ? bug in HSQLDB 2.0 ?
        Hide
        Milosz Tylenda added a comment -

        It usually works but fails with SQL syntax error in a rarely used case when you specify setFirstResults but not setMaxResults. I plan to address this next week.

        Show
        Milosz Tylenda added a comment - It usually works but fails with SQL syntax error in a rarely used case when you specify setFirstResults but not setMaxResults. I plan to address this next week.
        Hide
        Milosz Tylenda added a comment -

        Resolving so that it goes into 2.1.0 release notes. setMaxResults behaviour has been fixed. More fixes and doc update will be done in 2.2.0.

        Show
        Milosz Tylenda added a comment - Resolving so that it goes into 2.1.0 release notes. setMaxResults behaviour has been fixed. More fixes and doc update will be done in 2.2.0.
        Hide
        Albert Lee added a comment -

        Close issue in preparation for 2.2.0 release.

        Show
        Albert Lee added a comment - Close issue in preparation for 2.2.0 release.

          People

          • Assignee:
            Milosz Tylenda
            Reporter:
            Georgi Naplatanov
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development