openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Closed: (OPENJPA-1841) Allow DBDictionary to optimize IS [NOT] NULL SQL for specific data types.
Date Tue, 19 Oct 2010 18:40:28 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dick closed OPENJPA-1841.
---------------------------------

    Resolution: Fixed

> Allow DBDictionary to optimize IS [NOT] NULL SQL for specific data types.
> -------------------------------------------------------------------------
>
>                 Key: OPENJPA-1841
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1841
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 2.1.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 2.1.0
>
>
> Some databases do not support IS [NOT] NULL on all datatypes. 
> For example Sybase does not allow it's clob / blob types (TEXT and IMAGE respectively)
to be used with the IS NULL and IS NOT NULL clauses. The datalength() function to determine
if the column has any data instead of the generic IS [NOT] NULL clause. 
> Oracle has a similar restriction with BLOB / CLOB types. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message