Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1053961471.1228330064202.JavaMail.jira@brutus>
Date: Wed, 3 Dec 2008 10:47:44 -0800 (PST)
From: "Dinkar Rao (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-811) With Oracle, OpenJPA allows setting
 non-nullable field to null
In-Reply-To: <1903313414.1228329944450.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dinkar Rao updated OPENJPA-811:
-------------------------------

    Attachment: OPENJPA-811.patch

Submitting patch provided by Pinaki.

> With Oracle, OpenJPA allows setting non-nullable field to null
> --------------------------------------------------------------
>
>                 Key: OPENJPA-811
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-811
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 2.0.0
>            Reporter: Dinkar Rao
>         Attachments: OPENJPA-811.patch
>
>
> An entity has a field defined as follows:
> @Column(nullable=false)
> private Object  nonNullableObject;
> Using Oracle, it is possible to set the value of this column to null. OpenJPA will not complain, but will instead store whatever is returned by oracle.sql.BLOB.empty_lob().
> An exception should be thrown instead, because the field has been defined as non-nullable.

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