[
https://issues.apache.org/jira/browse/DERBY-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-3043.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
10.4.2.1
committed the change to the 10.4 branch and marked the issue resolved.
> 'Schema <schemaname> does not exist' when constraint used in table definition
> -----------------------------------------------------------------------------
>
> Key: DERBY-3043
> URL: https://issues.apache.org/jira/browse/DERBY-3043
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.1.4
> Environment: Mac OS 10
> Reporter: geoff hendrey
> Assignee: Bryan Pendleton
> Fix For: 10.4.2.1, 10.5.0.0
>
> Attachments: reorderWorkaroundTests.diff, setSchemaName.diff,
> withSimpleTest.diff
>
>
> 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__BLOGS__USERS(PK INTEGER NOT NULL GENERATED ALWAYS AS
> IDENTITY,username VARCHAR(16) NOT NULL CONSTRAINT
> BLOGSCOM__BLOGS__USERS_UNIQUE_username UNIQUE CONSTRAINT
> BLOGSCOM__BLOGS__USERS_PASSWORD_username CHECK(LENGTH(username)>7),password
> VARCHAR (32672) NOT NULL , PRIMARY KEY(PK));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
