Cayenne
  1. Cayenne
  2. CAY-1336

Oracle specific type support (oracle.sql.*)

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1M1, 2.0.5
    • Component/s: Core Library
    • Labels:
      None

      Description

      Official Oracle JDBC driver can return one of this specific type:

      http://download-east.oracle.com/otn_hosted_doc/jdeveloper/904preview/jdbc-javadoc/oracle/sql/package-summary.html

      Cayenne should handle it in right way.

      Related to CAY-1323 where was handled oracle.sql.Timestamp

      1. CAY-1336.patch
        8 kB
        Evgeny Ryabitskiy

        Activity

        Hide
        Evgeny Ryabitskiy added a comment -

        Committed to 3.1 trunk

        Show
        Evgeny Ryabitskiy added a comment - Committed to 3.1 trunk
        Hide
        Evgeny Ryabitskiy added a comment -

        Reopening this issues for 2.0 branch.

        Currently there is a regression for Oracle type support.

        I perform tests on 2.0.4 and 2.0.3 versions... on both there was standard Java types for CLOB and Timestamp.
        But in trunk (feature 2.0.5) it returns Oracle specific types.

        It was changed in tasks:

        CAY-672 Change the logic to get the Java class from ResultSetMetadata
        CAY-1052 Invalid cast on NUMERICs with scale of 0 using Postgres JDBC 8.2+

        So there is two ways:
        Add TypeMappings for all Oracle types to 2.0 like it was done in this issue...
        or add new type mapping logic like in CAY-1354

        Show
        Evgeny Ryabitskiy added a comment - Reopening this issues for 2.0 branch. Currently there is a regression for Oracle type support. I perform tests on 2.0.4 and 2.0.3 versions... on both there was standard Java types for CLOB and Timestamp. But in trunk (feature 2.0.5) it returns Oracle specific types. It was changed in tasks: CAY-672 Change the logic to get the Java class from ResultSetMetadata CAY-1052 Invalid cast on NUMERICs with scale of 0 using Postgres JDBC 8.2+ So there is two ways: Add TypeMappings for all Oracle types to 2.0 like it was done in this issue... or add new type mapping logic like in CAY-1354

          People

          • Assignee:
            Evgeny Ryabitskiy
            Reporter:
            Evgeny Ryabitskiy
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development