[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
>From your last comment I can't tell what you plan on changing to implement
>this. Are you
planni
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
What is the standard with respect to multi-column keys and the null uniqueness
semantics for this
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-2212:
--
Attachment: derby-2212preview.diff
This patch is not meant for commit.
Its just for review of
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-2212:
--
Attachment: derby-2212preview2.diff
Sorry for the delay in posting patch. It took me lot longer
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
I have only looked briefly at the most recent patch. I had not been following
this thread as the
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
How do you compare your current patch with a solution that instead used a
non-unique btree and the
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
i am not sure any of the following are problems, but things to think about.
These all stem from n
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
I continue to think that it is a bad idea to introduce duplicate values to the
current btree uniqu
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
Also is there some sort of functional spec for this. The initial description
seems to indicate th
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
Along the same lines in the case of multi-column keys, what null behavior is
being
implemented? I
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
There are 2 discussions here. Let's settle first what SQL level behavior is
being implemented. I
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
Derby currently does not support creating a unique constraint on a column with
nullable keys, and
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
I don't think I have explained very clearly why I don't think the current
approach is best. I espe
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
No, I don't think you have overlooked a compatibility issue. But you do
recogonize there
is a dif
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-2212:
--
Attachment: FunctionalSpec.html
Functional Spec for Unique Constraint
> Add "Unique where not
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
comments on 1st draft of functional spec:
1) In section "Proposed behavior of unique Constraint"
T
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-2212:
--
Attachment: FunctionlaSpecv2.html
In this version of functional spec I have removed all impleme
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-2212:
--
Attachment: FunctionalSpecV3.html
> Add "Unique where not null" to create index
> -
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
Attachment: FunctionalSpecV3_comment.html
FunctionalSpecV3_comment.html contains some typo/gram
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
I do want to say that once it is clear what the functionality is being
provided, it would be great
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2212:
---
Urgency: Normal
Labels: derby_triage10_10 (was: )
> Add "Unique where not null" to
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2212:
--
DERBY-3330 has been implemented which provides the SQL standard unique
constraint which allow mult
22 matches
Mail list logo
