db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Buğra Gedik (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-2212) Add "Unique where not null" to create index
Date Fri, 03 Nov 2017 03:15:01 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237024#comment-16237024
] 

Buğra Gedik edited comment on DERBY-2212 at 11/3/17 3:14 AM:
-------------------------------------------------------------

I would have used it, but the constraint is being generated by Hibernate. I wonder if I should
file a bug against Hibernate. It is generating a unique index statement. Is there a way in
Derby to create a constraint rather than an index after the table is created? If so, I can
suggest them to issue that command instead of ``create unique index``.


was (Author: bgedik):
I would have used it, but the constraint is being generated by Hibernate. I wonder if I should
file a bug against Hibernate. 

> Add "Unique where not null" to create index
> -------------------------------------------
>
>                 Key: DERBY-2212
>                 URL: https://issues.apache.org/jira/browse/DERBY-2212
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.2.1.6
>            Reporter: Oleksandr Alesinskyy
>            Priority: Major
>              Labels: derby_triage10_10
>         Attachments: FunctionalSpec.html, FunctionalSpecV3.html, FunctionalSpecV3_comment.html,
FunctionlaSpecv2.html, derby-2212preview.diff, derby-2212preview2.diff
>
>
> Derby prohibits creation of unique constraints on nullable colums (as well if only some
columns in the constraint list are nullable) and treat nulls in unique indexes as normal values
(i.e. only one row with null values in indexed columns may be inserted into the table). This
bahavior is very restrictive, does not completely comply with SQL standards (both letter and
intent) as well as with business needs and intending meaning of NULL values (2 null values
are not considered as equal, this comparision shall return NULL, and for selection criteria
boolean null is treated as FALSE).
> This behavior, as far as I can see, is modelled after DB2 (and differs from behavior
of most other major databases, like SyBase, Oracle, etc.).
> But even DB2 provide some means to alleviate these restrictions, namely "UNIQUE WHERE
NOT NULL" clause for CREATE INDEX statement.
> It will be very good if such "UNIQUE WHERE NOT NULL" clause will be introduced in Derby.
> Regards,
> Oleksandr Alesinskyy



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message