Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.4
    • Fix Version/s: core 1.4.4
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      When using an Oracle database, the following exception occurs when trying to create the table: ORA.00902: invalid datatype
      The problem is that Oracle doesn't support the data type BIGINT. Instead, LONG should be used.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        5d 22h 47m 1 Jukka Zitting 05/May/08 09:24
        Resolved Resolved Closed Closed
        246d 7h 36m 1 Jukka Zitting 06/Jan/09 16:01
        Jukka Zitting made changes -
        Workflow jira [ 12430008 ] no-reopen-closed, patch-avail [ 12468593 ]
        Jukka Zitting made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Jukka Zitting made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Jukka Zitting added a comment -

        Merged to the 1.4 branch in revision 653349.

        Show
        Jukka Zitting added a comment - Merged to the 1.4 branch in revision 653349.
        Jukka Zitting made changes -
        Component/s jackrabbit-core [ 12310114 ]
        Jukka Zitting made changes -
        Field Original Value New Value
        Fix Version/s core 1.4.3 [ 12313113 ]
        Fix Version/s core 1.4.4 [ 12313135 ]
        Hide
        Jukka Zitting added a comment -

        OK to commit to 1.4.4

        Show
        Jukka Zitting added a comment - OK to commit to 1.4.4
        Hide
        Thomas Mueller added a comment -

        It would be great to have this fixed in 1.4.4, should I commit it to the 1.4 branch?

        Show
        Thomas Mueller added a comment - It would be great to have this fixed in 1.4.4, should I commit it to the 1.4 branch?
        Hide
        Thomas Mueller added a comment -

        Fixed in revision 652306 (trunk)

        Show
        Thomas Mueller added a comment - Fixed in revision 652306 (trunk)
        Hide
        Thomas Mueller added a comment -

        Hi,
        You are right of course: NUMBER is correct. LONG doesn't work actually.

        > db2.properties
        Yes, please open an new issue.

        Show
        Thomas Mueller added a comment - Hi, You are right of course: NUMBER is correct. LONG doesn't work actually. > db2.properties Yes, please open an new issue.
        Hide
        Esteban Franqueiro added a comment -

        You're correct. But I used the following line in oracle.properties:
        createTable=CREATE TABLE $

        {tablePrefix}

        $

        {table}

        (ID VARCHAR2(255) PRIMARY KEY, LENGTH NUMBER, LAST_MODIFIED NUMBER, DATA BLOB)
        BTW, I also had to modify db2.properties. Should we open a new issue?

        Show
        Esteban Franqueiro added a comment - You're correct. But I used the following line in oracle.properties: createTable=CREATE TABLE $ {tablePrefix} $ {table} (ID VARCHAR2(255) PRIMARY KEY, LENGTH NUMBER, LAST_MODIFIED NUMBER, DATA BLOB) BTW, I also had to modify db2.properties. Should we open a new issue?
        Thomas Mueller created issue -

          People

          • Assignee:
            Thomas Mueller
            Reporter:
            Thomas Mueller
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development