Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-1133

DBDictionary.getPlaceholderValueString returns 0 for boolean which fails in PostgreSQL database.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 1.2.0, 2.0.0-M3
    • query
    • None
    • openJPA trunk.
      PostgreSQL 8.3
    • Patch Available

    Description

      When DBDictionary.getPlaceholderValueString is called with Types.BIT, it returns "0".
      PostgreSQL actually requires that a boolean be set. It cannot handle a numeric argument.

      Fix Description:
      Overriden DBDictionary.getPlaceholderValueString() inside PostgresDictionary to process Types.BIT correctly.
      Now, the method returns 'false' value when Types.BIT is passed as Column.type.

      Test case:
      The above bug is exposed from Kodo product which internally uses openJPA.
      When a query is made on a subclass using kodo api.
      Kodo generates an SQL ( with help of openJPA) that has UNION in it.

      It generates a SQL similar to the following:

      SELECT 0 FROM public.classA t0 UNION ALL SELECT t0.guidance FROM public.classB t0

      It got 0 from the openJPA DBDictionary.getPlaceholderValueString as the guidance data type is boolean.

      The above SQL will throw an exception in postgreSQL db saying:
      ERROR: UNION types integer and boolean cannot be matched.

      Attachments

        1. OPENJPA-1133_trunk.patch
          5 kB
          Ravi Prakash Palacherla

        Activity

          People

            rpalache Ravi Prakash Palacherla
            rpalache Ravi Prakash Palacherla
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: