This content has been marked as final. Show 7 replies
Double check if there is some condition in "validation Execution" tab of the UniqueKey validation.
no there is no exception in the validation execution but this happens always in unique validation when I try to edit null value the unique validator not fire.
is this a bug or what .
Hope you have Added Unique constraint on base the table. And in validation make sure Defer Execution to Transaction Level.
Edited by: Surendranath Kumar on Apr 17, 2012 4:25 PM
the unique constraint is added one the table on the data base and added on the entity level
the unique can't be added Deferred Execution to Transaction Level as this area is disable when I choose unique constraint.
and the unique not fired when I edit null field when I edit new filed or field that has value the unique is fired
I don't know where is the problem
Can you share the code. And also check; Due to null values, conditions are failing in side validation code; Even though validation event is fired and failing inside the code.
This example contains Script.sql, and this file contains script for employee table
The email column is unique and not mandatory
Double click employeeView1
Press Add to add new Employee
Add the Id , Last Name , "Sking" for the email and add other required fields
constrain will fire and error message will appear
Double click employeeView1 again
Go to EmployeeId 555
Change the email from null to "SKING"
"oracle.jbo.DMLConstraintException" will raise
This means that the unique constraint is not fired when updating null value. But when inserting or updating value that is not null the unique constraint is fired normally.
Is there any solution for this problem