Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3523

sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.4.1.3, 10.5.1.1
    • Fix Version/s: None
    • Component/s: SQL
    • Urgency:
      Low

      Description

      There are three messages which after Derby-3330 checkin now giving wrong information. These are

      42831:'

      {0}' cannot be a column of a primary key or unique key because it can contain null values.
      42Z20:Column '{0}

      ' cannot be made nullable. It is part of a primary key or unique constraint, which cannot have any null able columns.
      X0Y63.S:The command on table '

      {0}

      ' failed because null data was found in the primary key or unique constraint/index column(s). All columns in a primary or unique index key must not be null.

        Attachments

        1. derby-3523v1.diff
          16 kB
          Anurag Shekhar
        2. derby-3523v2.diff
          16 kB
          Anurag Shekhar
        3. derby-3523v3.diff
          14 kB
          Anurag Shekhar
        4. derby-3523-upgradetest.diff
          4 kB
          Anurag Shekhar
        5. derby-3523-upgradetest_v2.diff
          4 kB
          Anurag Shekhar

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                anurag Anurag Shekhar
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: