Data Modeler 3.0 EA1: Import deferrable foreign key

Importing from Data dictionary. Table has a deferrable initially deferred foreign key constraint.
Example:
create table didf( id number constraint didf_pk primary key deferrable initially deferred
, didf_id constraint didf_didf_fk references didf deferrable initially deferred
);Only primary key constraint is imported as deferrable.
didf_didf_fk is NOT DEFERRABLE in DDL Preview. Also after merge to a model the foreign key in physical model is not deferrable.

bug logged
Philip

Similar Messages

Data Modeler 3.0 EA1: Import deferrable column constraints

Importing from Data dictionary. Table has a deferrable initially deferred column constraints.
create table didmn( m number check (mod(m,2)=1) deferrable initially deferred
                  , mn number constraint didmn_modmn_chk check (mod(mn,2)=1) deferrable initially deferred
                  , constraint didmn_mnn_chk check (mn/m=3) deferrable initially deferred
                  , check (mn>m) deferrable initially deferred
                );Column level constraints are NOT DEFERRABLE in DDL Preview. Also after merge to a model they are in physical model not deferrable. As in my earlier foreign key thread Data Modeler 3.0 EA1: Import deferrable foreign key
Table level constraints are imported deferrable.
Edited by: Rafu on 19.10.2010 14:34

Hi Rafu,
EA2 is available and those DEFERRABLE problems are sorted out there.
Philip

Data Modeler - how can I define a foreign key but disabled

I am using SQL Developer Data Modeler Version 2.0.0 Build 570 on Mac OS X (Snow Leopard).
When defining a foreign key constraint, is there a way to define it as disabled?
When the DDL script is generated, the constraint is defined but it is always enabled, I want it to be disabled.
This is possible in the Jdeveloper data modeler, but I am missing the method to do this in SQL Developer Data Modeler.
Any help appreciated.

OraTone wrote:
I am using SQL Developer Data Modeler Version 2.0.0 Build 570 on Mac OS X (Snow Leopard).
When defining a foreign key constraint, is there a way to define it as disabled?
When the DDL script is generated, the constraint is defined but it is always enabled, I want it to be disabled.
This is possible in the Jdeveloper data modeler, but I am missing the method to do this in SQL Developer Data Modeler.
Any help appreciated.Create it and then disable it afterwards if you're using the Connections window to create them.
If you are generating the DDL edit the ENABLED keyword to DISABLED

Data Modeler 3.0 EA1: Importing domains and 2.0 model doesn't work

If I import (or open) a relational model from Modeler 2.0 which refers to domains, Modeler 3.0EA will not recognize the domains. I end up with a model full of "UNKNOWN" column types. I tried importing the domains first then importing the model, opening (or importing) the model and then the domains, and even importing the domains into the default domains set before opening the model. Nothing works; the column types will always be marked as UNKNOWN.
Is it me or a "known bug"?
Bert Laverman

Hi Bert,
Version 3.0 doesn't know anything about your domains - just copy defaultdomains.xml file from 2.0 installation (it's in datamodeler\domains directory) into 3.0 directory datamodeler\datamodeler\types.
Philip

Data Modeler 3.0 EA1 - Logical Relation to Foreign Key not generating

When use "Engineer to Relational Model" the only time it creates foreign keys from my relations is when those relations are of the type many-to-many. I've added a Primary UID for each table and I have tried to use the Apply Naming Standard options but nothing seems to work.
I tested my design with the design rules feature I have no errors.
Does anyone have any ideas?
Greg

Hi Greg,
probably you added primary uid after first engineering to relational model. You can check whether those uids are selected in engineering dialog.
Also you can check log file in datamodeler\datamodeler\log directory for logged problems there.
Philip

Object Types Attributes (Data Modeler 3.0 EA1.)

Hi,
Will the attribute object type support in data modeler be upgraded to the same functionality as column relational table support in 3.0? For relational columns I can attach a domain to a column, I can't attach a domain to an attribute in an object type. Also for a column I can define a 'Units', that is VARCHAR2 (30 BYTE) orVARCHAR2 (30 CHAR). If can't do this with the (Data Modeler 3.0 EA1.) for an object type's attribute. Will this be included?
Thanks,
Scott

Sue,
Thanks to you and your team for extending this to the object type (structured type) portion of SDDM 3.3 EA1 and 3.3 EA2. The object type portion of SDDM is pretty robust now for modeling and actually generating useable structures in the database (Oracle) now. With 3.3 EA2 at this point it will be much easier to take advantage of the object type features in the database and our applications. I have been waiting since Oracle version 8 for the tools team to provide a modeling tool that mirrors the functionality the server team has provided when it comes object types.
Thanks for this in SDDM 3.3 EA1 and SDDM 3.3 EA2!
ScottK

In ADF how can i insert data in multiple table if they have foreign key

I have started working on ADF and can anybody inform me in ADF how can i insert data in multiple table if they have foreign key,please?
Thnak you very much.

Hello,
Still no luck.I am surely doing silly mistakes.Anyway,Here are my workings-
1> student_mst (id(pk),studentname) and student_guard_mst(id(fk),guardianname)
2> created EO from both of the tables,made id in both EO as DBSequence and an association was also generated.
3> i made that association composite by clicking the checkbox
4> i created 2 VO from 2 EO.
5> put those VO in Application Module.
6> dragged and dropped 2 VO on my jspx page and dropped them as ADF Form.
Now what to do please?

Data Modeler 2.1 EA1 FK Constraints

Hi,
I don't know what functionality you have planed but, when I drag and drop the Master + Detail Table at the same time to the modeler window I see visually my FK Constraints. When I drag it one after the other I dont.
Most of the time I'm working on existing models. I would need the Model-Viewer to drag one table to the modeler window and have the opportunity to import all dependend tables and see all the FKs. Otherwise I wouldn't work with it but still work with JDeveloper.
Regards,
Juergen

Hi Philip,
Yes I'm talking about the viewer in 2.1 EA1
To be honest, I like the way Apex is doing it in the Object Browser / Model. You click on any table and it shows the first level dependency around it, you click on the dependend table and you get the first level dependencies of this table and so on.
So first level dependencies would be enough but I would like to have the opportunity to import a single table and tell Data Modeler import all first level dependency tables, then I want to click to a imported table and say, import all first level dependencies of this table, and so on..., just like Apex.
So first level would be a deal... :)
Juergen

Sql Developer Data Modeler 3.0 EA1: Auto route off

I admire that the data modeler tries to automatically position relationships and data flows. I am sure it is very hard to automate and I don't think it works very well in this tool.
So, I am happy that you have the option of turning "auto route" off as I am quite particular about how diagrams should look.
In the EA1 it seems that even with "auto route" turned of, all connected relationships and dataflows are automatically repositioned as soon as an entity or process box is resized or moved - even the tiniest bit.
I think the tool should not reposition relationships or dataflows as long as their current position can be maintained after the connected entity/process is resized or moved. When lines have to be moved the tool should try to maintain a position as close to its original position as possible.
Let me know if there is a way to achieve this.
Also, when relationships or dataflows have to be repositioned by the tool, I think they should be placed as far away from each other as possible (giving more room for labels). Currently, it seems that the default behavior is to lump relationships and dataflows close together when they connect the same entities or processes.
/ Marc de Oliveira

it's the same in Data modeler v. 2.0No, in version 2.0 it is not the same. The line stays in place if you move the entity or process in the same direction as the line, eg a vertical line is not repositioned if you move a connected entity or process vertically. The same goes for horizontal lines.
Also, when resizing the right side or the bottom side of an entity or process, lines connected to it are not repositioned (as long as the box does not become too small).
You can get lines "more" fixed if you introduce intermediate point Intermediate point? I never heard of that. Where do I learn more about that? I could not find it in the help file.
/ Marc de Oliveira

SQL Data Modeler 3.0 EA1 trying to create primary key on OT

Hi,
I'm trying to modify a primary key of an object table that was reversed (imported) from an Oracle 11.2.x RDBMS and am getting the error message "Incomplete Index definition". It is showing in the window "Index Columns Assignment". I get to the 'Primary Key Properties' window by pressing the 'Properties' button on the 'Table Properties' -> 'Primary Key'. If I try to edit the expression and then press the Ok or Apply buttons I get the error. With this be fixed in the production version? Will we be able to create a model in SQL Developer Data Modeler that generates a SQL statement similar to the following:
ALTER TABLE x_flags
ADD (CONSTRAINT x_flags_pk PRIMARY KEY (flags.id))
Thanks,
Scott K

Hi Scott,
I'm trying to modify a primary key of an object table that was reversed (imported) from an Oracle 11.2.x RDBMS and am getting the error message "Incomplete Index definition"... With this be fixed in the production version?yes
Will we be able to create a model in SQL Developer Data Modeler that generates a SQL statement similar to the following:
ALTER TABLE x_flags
ADD (CONSTRAINT x_flags_pk PRIMARY KEY (flags.id))I assume "flags" is column of object type and "id" is attribute of that type. I logged bug for that, so there will be support however not for 3.0.
Philip

Sql Developer Data Modeler 3.0 EA1: Preference- Naming standard- Templates

I am trying to figure out how the naming standard templates work.
When I go to:
Preference -> Naming standard -> Templates
It says that 'Attribute Relation' is '{ref entity} {ref attribute}'
What is the consequence of this?
I thought, it would mean that when creating a primary key attribute (ID) on an entity (DEPARTMENT), the related "foreign key" attribute (that is automatically created in related detail entities, such as EMPLOYEES) would be named DEPARTMENT ID.
Instead it is just called ID. Is that the intended behavior?
- Marc de Oliveira
Edited by: marc66 on 2010-10-29 05:59

Marc,
you should check "FK Attribute name synchronization" setting in "Preferences>Data Modeler>Model>Logical model" - probably it's checked and you cannot change the name of FK attribute.
I found another bug here - FK attribute doesn't follow changes in referred entity - I logged it in bug database. As workaround you can apply defined templates at entity level (there is button in entity dialog) or for whole logical model (using pop-up menu in the browser).
Philip

Import table data in right order to avoid violating foreign key constraints

Gentlemen
I am trying to import table data into an existing 10g schema using datapump import in table mode.
However, in order to avoid violating foreign key constraints, the tables must be loaded in a specified order. I tried specifying the order in the TABLES parameter:
TABLES=table1,table2,table3 etc.
However, datapump seems to chose its own order leading to errors like the following:
ORA-31693: Table data object "SCHEMAX"."TABLE3" failed to load/unload and is being skipped due to error:
ORA-02291: integrity constraint (SCHEMAX.TABLE3_TABLE1#FK) violated - parent key not found
I want to try to avoid having to disable all foreign keys because there are hundreds of them.
Any advice?
Yours
Claus Jacobsen, Denmark

Thanks Anantha.
Since I am only loadding data (the constraints are already defined in the target database), I am not sure whether this approach would work. Meanwhile I have solved the problem of moving data from one system to another using another, tedious and far from elegant approach that I would prefer to not eloborate on:-)
However, I have also discovered another probable reason why the foreign key constraints were violated, other than wrong order of table data loading. It turns out almost every single table in the schema contains a trigger supposed to generate a unique row ID from a sequence on insert such as:
CREATE OR REPLACE TRIGGER "SCHEMAX"."TABLEX#B_I_R"
BEFORE INSERT
ON TABLEX
FOR EACH ROW
DECLARE
BEGIN
SELECT tablex_seq.nextval INTO :NEW.ID FROM dual;
END;
If the import mechanism fires this trigger, and the sequences in the source and the target systems are not synchronized, then I guess that referred records a more than likely to end up with wrong ID's compared to the row ID's in the referring rows?
Spooky. Anybody can confirm this theory?
Yours
Claus
Message was edited by:
user586249

Creating a data model in BW by importing an .ER1 file

Hi,
We have a Data Model from an Oracle 9 data warehouse in the form of an Erwin File ( .ER1) . We would like to replicate this data model in SAP BW 7.0.
Is it possible to create the same data model in SAP BW by importing this file and automatically generating the data model in SAP BW ? . I understand this is possible in other datawarehouses but not sure if it is possible in BW .

I'm not sure why you need to call a method once the ArrayCollection gets the data. But what you can do is set the ArrayCollection's collectionChange event to an event handler, say
public function collectionEventHandler(event:CollectionEvent):void {
See Example: Modifying data in a DataGrid control @ http://livedocs.adobe.com/flex/3/html/help.html?content=about_dataproviders_5.html.

Data Modeler 3.0 EA1 - Logical= Attributes & Relational= Columns missing

Hi,
I imported Modeler 2.0 design into Modeler 3.0 EA1 and discovered that LOGICAL=>ATTRIBUTES and RELATIONAL=>COLUMNS options are no longer displayed.
Were these options removed from this new version or is my installation broken?
Thanks
Chiedu

Hi Chiedu,
they are removed. Your version is ok - at least for that :).
Philip

Sql Developer Data Modeler 3.0 EA1: Engineering relationships to relational

When doing 'engineer to relational model' the relationship names are converted directly to foreign key names.
So, when the relationship between EMPLOYEE and DEPARTMENT is called 'working in' then the generated foreign key is also called 'working in' (not event 'working_in').
Is it possible to have it engineered to something like 'employee_working_in_department_fk'?
- Marc de Oliveira

Obviously, a property called "Plural" and an option for engineering using "Plural" names instead of entity names.
This would also allow us to have a nice relationship report where we could translate relationships into natural languages, like this:
Each DEPARTMENT may be employing one or more EMPLOYEES.
/ Marc

Data Modeler 3.0 EA1: Import deferrable foreign key

Similar Messages

Maybe you are looking for