[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
----------------------------------
Attachment: derby-3330v3.diff
This patches fixes all the failures in test suite cased by this
work except for upgrades tests. I am still having failures and
errors in upgrade tests because this patch introduces extra
attribute in BTree and IndexRowGenerator.
II am also seeing one failure in
org.apache.derbyTesting.functionTests.tests.lang.PrimaryKeyTest.testKeyConstraintsImpliesNotNull
but I am getting this error in fresh checkout too.
I have made changes nist.dml019.out in group by tests.
Currently Unique constraint is backed by unique index
and group by clause on unique index internally uses distinct
scan resulting in sorted results. After changing backing
index from unique index to almost unique index distinct
index wasn't used and results appear in random order (similar
to group by clause on non unique indexes). I have modified the
out file to match the output of select with group by clause.
This results in deviation from current behavior but group by
without order by clause need not be sorted so portable
application will not be using this behavior or derby. Derby
manuals also don't promise this behavior.
This change in behavior doesn't mean that nist test is failing
as the test iis supposed to be checking only for the number
of rows and not their order.
> provide support for unique constraint over nullable columns
> -----------------------------------------------------------
>
> Key: DERBY-3330
> URL: https://issues.apache.org/jira/browse/DERBY-3330
> Project: Derby
> Issue Type: New Feature
> Components: Store
> Affects Versions: 10.4.0.0
> Environment: all
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Attachments: derby-3330.diff, derby-3330v2.diff, derby-3330v3.diff
>
>
> Allow unique constraint over nullable field. Right now derby support unique
> constraint only over not null columns.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
