[DERBY-3043] 'Schema <schemaname> does not exist' when constraint used in table definition

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.4.2.1, 10.5.1.1
• Component/s: SQL
• Environment: Mac OS 10
• Assignee: Bryan Pendleton
• Reporter: geoff hendrey
• Created: 03/Sep/07 18:00
• Updated: 21/Jan/11 17:50
• Resolved: 18/Mar/09 03:55

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));

Issue Links

• is related to: DERBY-4101 Further improvements to schema <schemaname> does not exist fix - DERBY-3043