[
https://issues.apache.org/jira/browse/DERBY-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640035#action_12640035
]
Dag H. Wanvik commented on DERBY-3043:
--------------------------------------
Tests look good to me.
+1
Small note: maybe it would be better to place those cases which would run
without the patch before
the cases that would not so they would not be "masked" if one tried to run this
test against an unpatched Derby?
> '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
> Attachments: 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.
