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

Similar Messages

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

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

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

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 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

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: Custom transformation script

What is the object model used by:
Tools -> Design Rules -> Transformations
From looking at the examples (and guessing) I have managed to create ID attributes on all my entities, but how do I set its sequence number or set it as the primary key?
entities = model.getEntitySet().toArray();
for (var e = 0; e<entities.length; e++)
entity = entities[e];
att = entity.createAttribute();
att.setName('ID');
- Marc de Oliveira

content of XML files:
1) class described, parent class if there is one
2)<property .../>
describes property - set and get method, data type of property, default value
3) <collection ... />
describes collection of objects belonging to class - 5 collections are defined in Table.xml - columns, indexes, table check constraints, column groups and spatial definitions
- get method - to get collection
- create item method - method of described class used to create item for that collection; so for columns collection table.createColumn() will create column in table
- other methods - add, move, remove if are defined
4)other meta data
definitions in 1) .. 4) are used by Oracle SQL Developer Data Modeler, so it'll be wrong to modify those xml files
5)<roproperty ../>
Data Modeler doesn't parse/process these definitions, we decided to not filter them out however you should not rely that much on them
6)some junk left
For each object you can set your own properties and they will be persisted (also included in compare/merge in versioning) together with other information for object - look at "template table" example in transformation scripts. Here are methods you can use:
void setProperty(String key, String value);
     String getProperty(String key);
     boolean hasProperty(String key);
     boolean hasProperty(String key, String value);
     void removeProperty(String key);
     void clearProperties();
     Iterator getPropertyNames();
Philip

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

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.

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

Generation of DDL similar to Oracle Designer (Data Modeler 3.0 EA1.)

Hi,
Will the production version of SQL Data Modeler allow the creation of separate DDL files similar to that which Oracle Designer does? For example, I can create a sequence number generator in Data Modeler (DM) and then make a call to that in an Object Type method. However the DDL file that is generated by DM has all DDL in one file. This would allow to take dependencies were taken into consideration, that is create the sequences before object types, packages and tables, then object type bodies, package bodies, etc...
Thanks,
ScottK

At this stage we do not support multiple files. We do plan to do this in the future. However you can work around this by repeating the DDL generation for the different objects types you want to have files for.
Remember that you can vote on the Exchange for your most desired features.
Sue

SQL Data Modeler 3.0 EA1 (Data Modeler 3.0 EA1.)

On the newest release of Data Modeler (3.0.0 Build 649), if I have a relational table with an object type structure, I still cannot pick one of the attributes in the structure to be part of a the primary key for the relational table. Oracle 11gR2 does allow this. Will this be added/included in 3.0?
Edited by: user4179829 on Oct 11, 2010 12:25 PM

Hi Scott,
EA2 is available and the problem is fixed there.
Philip

Data Modeling:Criteria to add a logical column to a DIM or FACT table

Hi,
Scenario:
Physical Layer:
- Table_T has following columns: COL_A, COL_B, COL_C
- COL_C is a measure. COL_A and COL_B refer to dimensions.
- COL_A is primary key of Table_A, COL_B is primary key of Table_B
BMM Layer:
1- Dimension table: DIM_A(TABLE_A), Fact table: contains COL_A, COL_B, COL_C
2- Dimension tables: DIM_A(TABLE_A), DIM_B(TABLE_B), Fact table: contains COL_A, COL_B, COL_C
Additional Information:
We can model the BMM layer using the above-mentioned approaches, but either of the two will have some advantages over the other to model COL_B. Some of the advantages of (2) as highlighted by the OBIEE team:
a). Drill down capability will be supported for COL_B,
b). Useful in scenarios where multiple facts need to refer to TABLE_B.
Concern:
We agree with the above technical comments but if someone can provide us with more insight on both the approaches and how an end user can benefit from either approach, it will help us a lot.
We basically need to understand what are the implications if we leave something as just an attribute on the fact and do not model it as a dimension.
Thank you,
Abhishek
P.S. The OBI Server Admin guide does provide us with useful information on the implementation aspect, but we need more information from the end user's perspective.

Very similar to the question below. In pure terms your FACT table should contain no Dimension attributes, Facts tables should contain measures.
Where you have a Physical table that contains a mixture of aggregates and non-aggregate Dimension Attributes then you should split them out in the logical layer into 2 Logical Tables one for the Fact one for the Dimension.
From an end user perspective (certainly the ones I have coached) it is easy for them to understand the the Measures are all in one place, and then if they need to slice and dice then they select the appropriate attributes from the Dimension folders.

Sql Developer Data Modeler 3.0 EA1: Process order/number

When opening my version 2.0 model in version 3.0 EA1, the process numbers are as I originally saved them.
After saving the model as a version 3.0 model (using "Save as..."), when I reopen that version all processes have been reordered on all levels of my model (about 300 processes).
Actually, it looks like 1 becomes 4, 1.1 becomes 4.4, 1.1.1 becomes 4.4.4 etc...
Strange behavior. Is there any way to avoid this?
/Marc de Oliveira

Hi Mark,
thanks for feedback. I logged bug for that.
Is there any way to avoid this?No for EA1 release.
Philip

Data Modeler 3.0 EA1: Import deferrable column constraints

Similar Messages

Maybe you are looking for