Devart Forums

Hi

If you're inserting data using the OraDeveloper Tools to Append a row, but the PK is generated on the server using a trigger (e.g. supplied from a sequence), you get the following error if you haven't refreshed the table since the last insert:-

Column 'ID' is constrained to be unique. Value '' is already present.

Yes the value of the new column is NULL because it was left blank, but it won't violate the constraint as the trigger will guard against this.

Thanks

Sorry for the delay.
Yes, this is a bug and we have already reproduced it.
Please wait for a new build with the fix.

This bug is already fixed.
Please download the recent version of OraDeveloper Tools.

.jp wrote:This bug is already fixed.
Please download the recent version of OraDeveloper Tools.

Hi

I still get this with 2.55.168. Is the fix present in this version?

Also, I get an error that a DATE column cannot be null, even though this is set to a default of SYSDATE in DDL.

Thanks

RobIntechnica wrote: I still get this with 2.55.168. Is the fix present in this version?
Thanks

Turn the paginal mode off.
This error still occurs if the paginal mode turned on. The fix of the error will be included in the future versions.

Also, I get an error that a DATE column cannot be null, even though this is set to a default of SYSDATE in DDL.

Yes, this is a bug. Fix of the error will be included in the future versions.