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

'Schema <schemaname> does not exist' when constraint used in table definition

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.3.1.4
    • 10.4.2.1, 10.5.1.1
    • SQL
    • None
    • Mac OS 10

    Description

      https://issues.apache.org/jira/browse/DERBY-568#action_12524420

      In the response to my original comment post, which you can find via the permalink above, I was encouraged to file this as a new issue.

      verified this back to 10.1.2.1 with the following ij script.

      connect 'jdbc:derby:wombat;create=true;user=blogs';

      CREATE TABLE BLOGSCOM_BLOGSUSERS(PK INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY,username VARCHAR(16) NOT NULL CONSTRAINT BLOGSCOMBLOGSUSERS_UNIQUE_username UNIQUE CONSTRAINT BLOGSCOMBLOGS_USERS_PASSWORD_username CHECK(LENGTH(username)>7),password VARCHAR (32672) NOT NULL , PRIMARY KEY(PK));

      Attachments

        1. setSchemaName.diff
          0.8 kB
          Bryan Pendleton
        2. withSimpleTest.diff
          5 kB
          Bryan Pendleton
        3. reorderWorkaroundTests.diff
          5 kB
          Bryan Pendleton
        4. tempTableTest.diff
          1 kB
          Bryan Pendleton

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-4101 Further improvements to schema <schemaname> does not exist fix - DERBY-3043

          • Major - Major loss of function.
          • Open

          Activity

            People

              bryanpendleton Bryan Pendleton
              geoff_hendrey geoff hendrey
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: