Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.1.0
    • Component/s: jdbc
    • Labels:
      None

      Description

      In order to execute FOR UPDATE statements against Sybase we create a special column named UNQ_INDEX.

      Some of our schema tools cause the column to be inserted twice (in memory). I've seen this happen with testcases which use the DROP_TABLES constant - but any code that uses the following persistence property could see the same behavior :
      openjpa.jdbc.SynchronizeMappings=buildSchema(ForeignKeys=true,SchemaAction='drop,add')

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Michael Dick
            Reporter:
            Michael Dick
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development