Page 1 of 1
How to change constraint names
Posted: Wed 12 Nov 2014 18:56
by mfriend
Hi Folks:
I like to give 'custom' names to all of my constraints.
Oracle gives default constraint names to check constraints that look like the following:
If I right click on the constraint name and choose "Edit Constraint" I get the following:
The only problem is the name (like SYS_C0014960) is read only it seems. I am logged in as a user that has the right permission level. Am I missing something on how to rename these?
Matthew
Re: How to change constraint names
Posted: Thu 13 Nov 2014 15:34
by alexa
We will fix this issue in one of the next product builds and will notify you once it's available for downloading.
Re: How to change constraint names
Posted: Thu 13 Nov 2014 15:49
by mfriend
That's awesome, thanks.
Re: How to change constraint names
Posted: Fri 30 Jan 2015 14:17
by alexa
We would like to let you know that we have released a new version 3.7 of dbForge Studio for Oracle where the issue you reported is fixed
http://www.devart.com/dbforge/oracle/st ... nload.html
Thank you for your help in improving dbForge Studio for Oracle.
Re: How to change constraint names
Posted: Thu 12 Feb 2015 07:45
by babamithan
Hello, I recently migrated my application to the 8.4.171 version and I get the following error when running a Linq query "ORA-12704: character set mismatch".
If I check the history of updates, it indicates that this problem has been fixed with Version 7.9.333! ...
Another subsidiary question: Where did the Data.Oracle.Entity.OracleEntityProviderServices.TypedNulls property?
Thank you for your answer
____________________
http://www.win-on-slots.com/
Re: How to change constraint names
Posted: Fri 13 Feb 2015 15:42
by Shalex
babamithan wrote:I recently migrated my application to the 8.4.171 version and I get the following error when running a Linq query "ORA-12704: character set mismatch"
Please refer to
http://forums.devart.com/viewtopic.php?t=31063.
JIC: you can find out the generated SQL with dbMonitor (
download link,
documentation).
If this doesn't help,
send us a small complete test project with the corresponding DDL/DML script of database objects to reproduce the issue in our environment.