NOT NULL Unique Constraint in Data Modeler

I've created Unique Constraints in the Relational Model and I'm trying to figure out how to make it a NOT NULL constraint.
Let's say the table name is category with columns cat_id, cat_name, sort.
In SQL I create "ALTER TABLE category MODIFY (category CONSTRAINT xxx_cat_name_nn NOT NULL);", but inside the modeler there is no data entry points in the [Unique Key Properties - xxx_cat_name_nn] dialog box, that I can find, that lets me tell it that it is a NOT NULL constraint. I'm sure there is a way but I'm just fall over my own feet trying to find it.
Any help would be greatly appricated.
Edited by: 991065 on Feb 28, 2013 1:40 PM

Hi,
You can make the column NOT NULL by unsetting the "Allow Nulls" property for the Column.
If you want a named NOT NULL Constraint, you should also set the "Not Null Constraint Name" property (on the Default and Constraint tab of the Column Properties dialog).
David

Similar Messages

Primary key and relevant not null check constraints....

Hi ,
There are some constraints of primary key type and not null check constraints on columns which constitute each primary key....
Should I/Do I have to drop them....????
Do they burden the db at the time of data validation....????
Thanks...
Sim

Hi,
>>There are some constraints of primary key type and not null check constraints on columns which constitute each primary key..
In fact, a column that constitutes a primary key, by default cannot accept NULL values. In this case, defines a PK column as NOT NULL would not be necessary.
LEGATTI@ORACLE10> create table x (id number constraint pk_x primary key);
Table created.
LEGATTI@ORACLE10> desc x
Name                  Null?    Type
ID                    NOT NULL NUMBER
LEGATTI@ORACLE10> select constraint_name,constraint_type,table_name,search_condition from user_constraints where table_name='X';
CONSTRAINT_NAME                C TABLE_NAME      SEARCH_CONDITION
PK_X                           P X
LEGATTI@ORACLE10> create table y (id number not null constraint pk_y primary key);
Table created.
LEGATTI@ORACLE10> desc y
Name                  Null?    Type
ID                   NOT NULL NUMBER
LEGATTI@ORACLE10> select constraint_name,constraint_type,table_name,search_condition from user_constraints where table_name='Y';
CONSTRAINT_NAME                C TABLE_NAME      SEARCH_CONDITION
SYS_C006327381 C Y "ID" IS NOT NULL
PK_Y                           P Y
LEGATTI@ORACLE10> alter table y drop constraint SYS_C006327381;
Table altered.
LEGATTI@ORACLE10> desc y
Name                                      Null?    Type
ID                                        NOT NULL NUMBER
LEGATTI@ORACLE10> insert into y values (NULL);
insert into y values (NULL)
ERROR at line 1:
ORA-01400: cannot insert NULL into ("LEGATTI"."Y"."ID")
LEGATTI@ORACLE10> insert into y values (1);
1 row created.
LEGATTI@ORACLE10> insert into y values (1);
insert into y values (1)
ERROR at line 1:
ORA-00001: unique constraint (LEGATTI.PK_Y) violated
>>Should I/Do I have to drop them....????
I don't see any problem, otherwise, drop the NOT NULL constraint is the same with alter the column table like below:
LEGATTI@ORACLE10> create table z (id number not null constraint pk_z primary key);
Table created.
LEGATTI@ORACLE10> select constraint_name,constraint_type,table_name,search_condition from user_constraints where table_name='Z';
CONSTRAINT_NAME                C TABLE_NAME                     SEARCH_CONDITION
SYS_C006328420 C Z "ID" IS NOT NULL
PK_Z                           P Z
LEGATTI@ORACLE10> desc z
Name                                      Null?    Type
ID                                        NOT NULL NUMBER
LEGATTI@ORACLE10> alter table z modify id NULL;
Table altered.
LEGATTI@ORACLE10> select constraint_name,constraint_type,table_name,search_condition from user_constraints where table_name='Z';
CONSTRAINT_NAME                C TABLE_NAME                     SEARCH_CONDITION
PK_Z                           P Z
LEGATTI@ORACLE10> desc z
Name                                      Null?    Type
ID                                        NOT NULL NUMBERCheers
Legatti

Adding a *Not* Null Entry to a Data-Bound Drop Down List

How do I add a not null entry to a data-bound drop down list? I am supposed to have something like this:
<html:select property="Korisnik1" >
<html:option value="0000">
(Not null value)
</html:option>
<html:option value="-1">
(Null value)
</html:option>
<html:optionsCollection label="prompt" value="index" property="Korisnik1.displayData" />
</html:select >
In case the value 0000 is marked the value should be inserted in to the database. The code above displays the value but insert doesn't work.

I think that in this case that article is not what's required Shay as the question related to a "No Null" entry. The answer would be to add it into the list that is used to populate the list in the first place - generally by adding a "union select from dual" to the query that generates the list values.

J2sdk1.4.2_12 does not support the 64 bit data model

Hi guys,
I need support for instalation NW2004R1 for windows x64bit.
in the step "define parameters" I need set JDK Directory, I setting C:\j2sdk1.4.2_12 and when click in botton next, I receive the message " The JDK installed in directory C:\j2sdk1.4.2_12 does not support the 64 bit data model. Choose a different JDK. "
I search documents but not found.
Anybody can help-me ???
thanks
Henrique Mattos.

Hi,
You can get more information related to your issue from
service.sap.com
https://sdlc2e.sun.com/ECom/EComActionServlet;jsessionid=606D9ABC1A37F8F6D7517A9B77ACA38B
Regards
Agasthuri Doss

Check constraint in Data Modeler

Hi
I have a problem with merging two logical models.
in first I have a table with column ranking number(2),
in second model I modify this column:
ranking varchar2(10) default 'A'
and create check constraint ranking_ch:
ranking..... check ('A', 'B',.....)
Then I compare models I have only
alter table....
modify ranking varchar2(10) default 'A'
but I have not constraint ranking_ch.
Why?

Thanks.
Another topic:
I have a problem with reverse engineering with Data Modeler:
1.I have a simple script (*.sql):
create table jw
(a number(2),
b varchar2(30)
2.I use function file/import/ddl file - on Relational diagram is OK:
I have table with two columns.
3. I use function Engineer to Logical Model and I see entity with:
a numeric_0_2_0
b varchar_0_0_30
Modeler creates two new domains.
Why?

NWDS does not open Webdynpro Component's Data Modeler

Hi,
All of a sudden my kindly Tool does not open any of the Component's Data Modeler for Mapping attributes. It happened all of a sudden. I cleaned everything and reinstalled from a proper software.
If any one has a solution kindly let me know or if you can direct me to appropriate forum or Weblog to recover it will be a great help.
-Shekhar

HI Shekher...
May be following link will helpful to u...U see some basic tutorial in this link that will help u abt webDynPro.....
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d
Also I m Giving U some Basic IDEA abt Data-Modular.
Data Modeler
Features
The Data Modeler is a graphical tool and part of the range of Web Dynpro tools. Using the Data Modeler provides you with efficient support for a number of central development tasks.
·        Creating a View
·        Controller definition
·        Declaring a Model to the Component
·        Nesting Components
·        Creating a Data Link
·        Working with View Templates
·        Working with the Service Controller
The perspective area that displays the Data Modeler is the Diagram View. The entities of a Web Dynpro application are created using graphical means. A selection list of Data Modeler actions is available from which you select the relevant entity and insert it in the design area of the Data Modeler.
Starting the Tool
Prerequisites
You have created a Project and a corresponding root Web Dynpro Component.
Procedure
To open the Data Modeler, choose Open Data Modeler from the context menu for the component name in the Web Dynpro Explorer. To create an application entity, choose the corresponding Data Modeler action in the tool selection area. Then click on the relevant area in the Data Modeler editor. The corresponding wizard is then started and you can make the required entries.
For example, to define a custom controller, choose Create Custom Controller and then click on the area Custom Controllers. The definition wizard is started automatically.
If This is not the case then plz check ur WebDynPro Installation Manual....
Hope So ur problem will Solve.....:-)
Regard's
Dheerendra Shukla

Unique constraint is not thrown when used MERGE INSERT (alone) via dblink.

We found some interesting behaviour of unique constraint on Merge query when we use Merge When Not Matched Insert (no update query) via a dblink.
In one Schema S1, on Table A1(c1,c2,c3) there is a unique constraint on column (c1,c2).
Column c2 is nullable and has null for some records.
Now i have a table A2 with same defintion as A1 in Schema S2.In S2 , i have a dblink of S1 as S1 itself.
I have data in S2.A2. Here also i have some records with c2 as null and c1 matching with the data of S1.A1.
Now from schema S2,
I am using the following Merge Query,
MERGE INTO S1.A1 target
USING S2.A2 source
ON (target.c1 = source.c1 and target.c2 = source.c2)
WHEN NOT MATCHED
INSERT (c1,c2,c3) values (source.c1, source.c2,source.c3)
WHEN MATCHED
UPDATE c3 = source.c3;
Now when i execute this merge in schema S2,
if i have some data in S1.A1 and S2.A2 having c1 as same and c2 as null, as oracle does not treat two nulls same, it goes for an insert, i have got unique constraint violated error.
But if i execute MERGE INSERT alone, though that record is getting inserted , i am not getting unique constraint violated error.
Oracle version we are using is 10g (10.2...).
Is it a bug in oracle or what could have caused this behaviour.

Dear,
ERROR at line 1:
ORA-00001: unique constraint (SYS_C00137508) violatedYou need to think about two things
(a) read consistency : what was the situation of table_1 when the maching clause has been initially evaluated ; there were 0 rows matching which means the merge operation will be all insert
(b) your matching clause has a problem : the join column must be unique in both tables otherwise the merge will be ambigous. You don't have a unique key on the source table
(c) think that the merge operation will never insert id =1 and then update id = 1 within the same operation. This will never happen
Hope this helps
Mohamed Houri

Not able to save a newly created Data Model in BI Publisher.

Hello everyone,
I was trying to create a new Report (my very first report) in BI Publisher. I created a new Data Model and a Data Set. But I am not able to save the Data Model and thus not able to proceed to the report. There's no error shown. Same happens with reports too.
Kindly provide me with a solution.
Regards
Ash
Edited by: 902739 on 28-Dec-2011 01:02

You should have a group called 'XMLP_ADMIN' in your repository and administrator or the user you are using should be part of that group. Look into paint.rpd for all these.

Unique Constraint Not Allowed in OA Table design?

Is it really true or is just my OApps Admin /DBA is just plain stupid for not allowing unique constraint at table level?
I have to implement a EO attribute level validation that does a select on an unindexed field thru the List Validator feature.
The problem is it is taking 40-60 seconds to commit something to the EO.

Thats true, if talking about only OAF, you don't need the constraint as you can handle that in code!
--Mukul

How to know if the data model qry is not returning any data

Hi
If my report doesn't have data (meaning if the data model qry doesn't retreive any data), I wan't to show this text: "There is no data returned."
My question is how would I know that the qry is not returning any data. I know I can create a text field, and write a trigger on it, to set it True or False depending on the fact that data is being returned or not.
Thanks
Shalu

Hi,
In Data Model create a summary column for function=count on one of your columns.
Then for BeforeReport trigger you can write
function BeforeReport return boolean is
begin
if :CS_RPT_NODATA > 0 then
return (TRUE);
end if;
SRW.MESSAGE(300,'There is no data');
return (FALSE);
end;
Regards, Gicu

SQL Data Modeler bugs (or only misused?)

Hi,
I think I ran into some modeler bugs and missing features ...
BTW: is there a place where all the known bugs are listed?
* although "no action" was selected in "General Options - Model - Relational" for foreign keys all the foreign keys are created with
"not deferrable" (well, why not, if it makes the modeler happy) and
"on delete set null" (thats not what I'd call "no action")
* DDL statements for indexes lack the schema name
* newly generated foreign relations are not always displayed in the relational model
* DDL preview for syncing physical model with relational does not (always) work (well - so far it worked once)
steps taken: File - Import - Data dictionary, selected objects for import, correct target model chosen, "swap target model" checked
* foreign keys in unique constraints are always set to "not null" (in logical and physical model)
* no trigger/constraint created for ARCs (I am not sure about this, but IIRC I did not see anything making an ARC really work)
Or do ARCs simply not work yet?
* modeler hangs sometimes (e.g. when opening "Save as" dialog etc.)
* dialogs are opened outside visible pane when the position of monitors is changed (the dialogs seem to remember their last position)
* sequences (physical model withing relational model) are loosing their user
* missing multi schema capabilities :-(
* the layout capabilities - pardon my french - suck
Especially that the boxes and lines seem to wander around from one usage to the next (entities aligned with grid - next start the entities are no longer aligned).
And if you ever need to save/export the model somewhere else all the references stick to a single connection point.
Not to mention a simple move of a box ...
Thank you for your effort
Peter
Edited by: stueckl on Sep 3, 2009 9:41 PM

Hi Philip,
sorry for not answering quite a time ...
Just some prerequisites ;-) ...
- Target database: Oracle 10g R2 (10.2.0.4)
- Modeler version 2.0.0 build 570
- model creation method: logical model, relational model, (physical model), Database objects
- OS WindowsXP German, SP3
- JDK Sun Java 1.6, build 1.6.0_16-b01
* nullable FK column in unique keys
meanwhile I found out, how to achieve that - but IMHO the steps to take are quite cumbersome
1) make a FK relation with "target optional" checked on the Cardinality page of the FK properties
2) open entity properties, check attributes of FK column (it says: nulls allowed - the checkbox cannot be changed)
3) got to unique identifiers page and add a unique identifier
4) open the unique identifier property dialog and add the foreign key
5) close both property dialogs
6) reopen the entity property dialog, check attributes of FK column (it says: no nulls allowed - the checkbox cannot be changed)
7) check the FK properties: it still says: target optional (it is checked)
8) check the graphical representation of the FK key: dashed line at target entity (meaning: optional)
9) create the relational model: the FK column is created with "not null"
10) go back to logical model
11) change FK property to: target mandatory (uncheck "target optional")
12) create relational model
13) change FK property to: target optional (check "target optional")
14) create relational model
15) SUCCESS! the foreign key column is now nullable
BUT: you never ever must change ANY of the entities properties or you must redo steps 11 to 15
* "no action" of FKs
I will look into that. Thanks for the suggestions.
* DDL statements for indexes
Sorry for being imprecise ... I was talking about automatically generated indexes (for unique and foreign keys).
Those don't show up in the index listing of the tables in the physical model (probably, because they are automated).
But why do I have to set the default schema for indexes again? The tables get the schema information for the default schema (General Options - Model - Physical) but not the indexes :-(.
Generated DDL snippet:
CREATE TABLE ZCBC1ST1.ZCBRAGIT_AGENDAITEM ( ...
CREATE UNIQUE INDEX ZCBSAgIt_U1X ON ZCBC1ST1.ZCBRAGIT_AGENDAITEM ( ...
Same for FK indexes. And the unique index property page in the physical table section does not let me specify a schema owner (OK for me, because the unique key is created by an "alter table" statement).
* ARC trigger
My bad - I only checked "DDL preview" of the table, which doesn't show the ARC trigger. The complete generation does. Sorry.
* "missing multi schema capabilities" and "sequences loose owner"
Please excuse a newbie blush.
I just found out I can change the table owner using the physical model capabilities (I guessed I used way too long PowerDesigner V6 ;-) ).
BUT ...
The newly created user does not "survive" a "save all - close all - open" sequence on "Physical Models" ... only closing the app or saving the Oracle10g physical model makes the user persistent.
And also ... if the new table or sequence owner is the first in the drop down list on the property dialog, the user is replaced by an automatically created new user (e.g. User4, User5, and so on).
Example:
* I have three defined users and the standard "MDSys" and "Public".
* My three users are named ZCBC1ST1, ZCBCCore and ZCBCDial (those names are because i need to follow naming rules).
* ZCBC1ST1 is my default physical model user, which was set in "General Options"
* ZCBC1ST1 is the first in each drop down list.
* I have some sequences named Seq1, Seq2, Seq3 and Seq4
* Seq1 was given to ZCBC1ST1, Seq2 to MDSys, Seq3 to ZCBCCore and Seq4 to ZCBCDial
* saved and closed the Oracle10g physical model and reopened it
* Seq1 now has User4, but the other have still the users they were attached to
The same applies to tables - I am unable to give a table to the first entry of the user list.
Solution I found to this problem ...
1) remove the default physical user in "General Options" (and never ever set it again)
2) create a explicit user (with the name of the prior default user)
3) manually reattach all objects to this user sigh
4) so far not a problem with automatically generated indexes, because they don't use the default user anyway
* newly generated FKs not shown in relational model
I had this odd behaviour several times.
1) Logical model: adding a new FK relation
2) giving the reference-column a pretty relational name
3) generating the relational model
4) rather often the new column shows up in the relational model but the arrow for the new foreign key does not.
5) only after i open the properties dialog of the missing foreign key the arrow is shown in the model
6) happens often to sub-models - less often to the top-model
* model syncing (Oracle10g with modeler)
As Ms. Harper stated in one of her posts (and she even made a video tutorial IIRC) it should be possible to sync a Modeler model with the Oracle10g contents.
AFAIR the tutorial showed only how to sync the model with the contents but not vice versa.
I tried to achieve this checking the "swap target model" check box (that's the important thingy) of the import dialog. Everything worked fine besides there is only a preview of DDL statements available but no "Merge" or "Create DDL Statement". And exactly that preview doesn't seem to work anymore. No matter what objects I select, I am unable to see any DDL statements to upgrade the Database.
I don't know why, but it worked again just before. I will keep an eye on this. ;-)
So much for now ...
Thank you for your effort
Peter
Edited by: stueckl on Sep 9, 2009 1:03 PM

Unique constraint error but key when inserting unique keys!

Hi,
I am tring to update an existing database with some older data, I am getting an error which complains about a unique constraint being violated although there is no voilation evident after testing.
I am puzzled by this and was wondering if someone could give me any extra info on another possible cause.
I googled but found that this error is caused by duplicating primary keys which I am not doing though I still get this error.
I run this query then the update and get the output below:
desc test_sales;
desc sales_order;
SELECT order_id FROM sales_order WHERE order_id IN (SELECT order_id FROM test_Sales);
INSERT INTO sales_order
(order_id,order_date,customer_id, ship_date,total)
SELECT
      order_id,
      order_date,
      cust_id,
      ship_date,
      total
FROM
      test_sales;
desc test_sales;
Name                           Null     Type
------------------------------ -------- CUST_ID                                 NUMBER(6)
OLD_SYSTEM_ID                           VARCHAR2(25)
DESCRIPTION                             VARCHAR2(35)
ORDER_DATE                              DATE
SHIP_DATE                               DATE
QUANTITY                                NUMBER
ORDER_ID                       NOT NULL NUMBER(4)
ITEM_ID                        NOT NULL NUMBER(4)
SITE_COUNT                              NUMBER(2)
TOTAL                                   NUMBER(8,2)
PRODUCT_CODE                            NUMBER(6)
LIST_PRICE                              NUMBER(8,2)
12 rows selected
desc sales_order;
Name                           Null     Type
------------------------------ -------- ORDER_ID                       NOT NULL NUMBER(4)
ORDER_DATE                              DATE
CUSTOMER_ID                             NUMBER(6)
SHIP_DATE                               DATE
TOTAL                                   NUMBER(8,2)
5 rows selected
ORDER_ID
0 rows selected
Error starting at line 7 in command:
INSERT INTO sales_order
(order_id,order_date,customer_id, ship_date,total)
SELECT
      order_id,
      order_date,
      cust_id,
      ship_date,
      total
FROM
      test_sales
Error report:
SQL Error: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 8
ORA-00001: unique constraint (MICHAELKELLY.SYS_C00210356) violatedMessage was edited by:
Mike1981
Message was edited by:
Mike1981

ORA-00001: unique constraint (MICHAELKELLY.SYS_C00210356) violated
=> check dba_cons_columns to see what the constraint actually exists off

Bulk table update returning ORA-00001: unique constraint

I'm trying to update every record in a PROPERTY table that has a CLASS of either 1 or 9 and a STATUS of 'LHLD'. CLASS and STATUS descriptor records are in different tables to the PROPERTY table but reference the PROPERTY records by the PROPERTY tables unid.
I have wrote the following update command,
UPDATE RNT_PROPERTY_DESCRIPTOR SET DESCRIPTOR = 'PROP', DESCRIPTOR_VALUE = '1', EFFECT_DATE = '01-APR-04', USER_ID = 'USER'
WHERE RNT_PROPERTY_DESCRIPTOR.UNID IN (SELECT PROPERTY.UNID FROM PROPERTY, PROPERTY_CLASS_STATUS
WHERE PROPERTY_CLASS_STATUS.PROP_CLASS = '1'
OR PROPERTY_CLASS_STATUS .PROP_CLASS = '9'
AND PROPERTY.UNID IN (SELECT PROPERTY.UNID FROM PROPERTY, PROP_STATUS_HIST
WHERE PROP_STATUS_HIST.code = 'LHLD'));
However, after executing for around 10 mins the process update fails and the following error is returned:
ORA-00001: unique constraint (RNT_PROPERTY_DESCRIPTOR_IDX) violated
I know that the IDX suffix refers to the table INDEX but I'm not sure why I'm getting a key constraint, none of the colums that I'm trying to update must be unique.
For info the PROPERTY table has around 250,000 rows.
Any ideas? Is there an error in my update statement?
Thanks in advance.

Gintsp,
can you explain a little more? I'm not sure what you are suggesting that I try.
Here is the output of what I have tried
SQL> UPDATE RNT_PROPERTY_DESCRIPTOR SET DESCRIPTOR = 'PROP', DESCRIPTOR_VALUE = '1', EFFECT_DATE = '01-APR-04', USER_ID = 'USER'
2 WHERE RNT_PROPERTY_DESCRIPTOR.UNID IN (SELECT PROPERTY.UNID FROM PROPERTY, PROPERTY_CLASS_STATUS
3 WHERE PROPERTY_CLASS_STATUS.PROP_CLASS = '1'
4 OR PROPERTY_CLASS_STATUS.PROP_CLASS = '9'
5 AND PROPERTY.UNID IN (SELECT PROPERTY.UNID FROM PROPERTY, PROP_STATUS_HIST
6 WHERE PROP_STATUS_HIST.CODE = 'LHLD'));
UPDATE RNT_PROPERTY_DESCRIPTOR SET DESCRIPTOR = 'PROP', DESCRIPTOR_VALUE = '1', EFFECT_DATE = '
ERROR at line 1:
ORA-00001: unique constraint (RNT_PROPERTY_DESCRIPTOR_IDX) violated
SQL> select owner, constraint_type, table_name, search_condition from user_constraints where constraint_name = 'RNT_PROPERTY_DESCRIPTOR_IDX';
no rows selected
The RNT_PROPERTY_DESCRIPTOR table structure is as follows:
Name Null? Type
UPRN NOT NULL NUMBER(7)
DESCRIPTOR NOT NULL VARCHAR2(4)
DESCRIPTOR_VALUE VARCHAR2(11)
EFFECT_DATE NOT NULL DATE
VALUE_DESCRIPTION VARCHAR2(35)
POINTS NUMBER(2)
POUNDS NUMBER(5,2)
SUPERSEDED VARCHAR2(1)
CURRENT_FLAG VARCHAR2(1)
FUTURE VARCHAR2(1)
END_EFFECT_DATE DATE
USER_ID NOT NULL VARCHAR2(10)
CREATE_DATE DATE
-------------------------------------------------------------

Bug report SQL DEVELOPER DATA MODELER

Hello,
I think i found a bug using Sql developer data modeler 2.0.0 build 584.
When importing a DDL file to create a relational model, foreign key constraints might not be created if foreign key uses multiple-field and the fields are not referenced in the same order as the primary key was.
ex:
Table FOO ..... PRIMARY KEY (id_1, id_2)
FOREIGN KEY (id_2, id_1) REFERENCES FOO (id_2, id_1)
Benjamin
P.S: Bellow is a portion of SQL code demonstrating the problem:
-- "_decompte"
CREATE TABLE "_decompte"(
numero_rang VARCHAR2(2),
numero_contrat VARCHAR2(13),
id_decompte VARCHAR2(19)
ALTER TABLE "_decompte"
add CONSTRAINT pk_decompte PRIMARY KEY (numero_rang, numero_contrat, id_decompte);
-- "_decompte_detail"
CREATE TABLE "_decompte_detail"(
numero_rang VARCHAR2(2),
id_ligne NUMBER(4),
numero_contrat VARCHAR2(13),
id_decompte VARCHAR2(19)
-- "_decompte_detail"
-- NOT Recognized by SQL DEVELOPER DATA MODELER (fields are not in the same order as primary key definition)
ALTER TABLE "_decompte_detail"
add CONSTRAINT fk_decompte_detail_1 FOREIGN KEY (numero_contrat, numero_rang , id_decompte) REFERENCES "_decompte"(numero_contrat, numero_rang , id_decompte);
-- Recognized by SQL DEVELOPER DATA MODELER
ALTER TABLE "_decompte_detail"
add CONSTRAINT fk_decompte_detail_2 FOREIGN KEY (numero_rang, numero_contrat, id_decompte) REFERENCES "_decompte"(numero_rang, numero_contrat, id_decompte);

Hi,
Well, I was recently given some database scripts and asked to correct and improve them. These scripts were not generated but rather hand made. Having no access to a DBMS I was just curious about the result of this option in Data modeler and tried it for a better DB overview. I don't need it at all, but I was surprised to discover that the result was a failure. So I tried various scripts until I found the mistake.
regards.

MySQL functionality within Oracle SQL Developer Data Modeler

Hi all,
I've read a few forum posts here that lead me to believe that MySQL is not currently supported by the data modeler tool (Link #1 I got to by clicking on the Statement Of Direction link on the main page SQL Developer Data Modeler</title><meta name="Title" content="SQL Developer Data Modeler"&g… Link #2 I got to by doing a search on the word MySQL within the forum search):
Link 1:
SQL Developer Data Modeler Statement of Direction
Link 2:
Can datamodeler be used with MySQL?
SQL Developer (not the Data Modeler tool, but the database admin-type tool not for modeling) does support MySQL using the latest MySQL Connector J 5.1 driver but, strangely, it doesn't seem the Data Modeler supports it, though. Can anyone please confirm that MySQL is currently unsupported for the Data Modeler tool? Thanks in advance.

Hi,
it doesn't seem the Data Modeler supports it, though.
Data Modeler doesn't have specific support for MySQL - i.e you cannot generate DDL for MySQL. Though you can import form MySQL server using JDBC connection in standalone DM or using created MySQL connection if you are using DM inside SQL Developer.
You can import definitions for tables(columns, PK and UK constraints, indexes, foreign keys) and views.
Philip

NOT NULL Unique Constraint in Data Modeler

Similar Messages

Maybe you are looking for