IDM person centric data model

HI,
We are using Sun IDM to do provisioning for an service provider. The data model differs from the standard user view, where one Person has many Accounts on many Resources.
The data model we are trying to represent is complicated: but simply it is Person has many Credentials, that each link to many Roles. A persons Role(s) link the 3 entities Service, BillingAccount and Person, and describe what that Person is to that Service or BillingAccount. Eg user, account payee, account authority etc.
How can we represent this in Sun IDM. I have looked at Scripted JDBC connector and it's ability to map user Account properties to a database as two or more tables but this doesn't seem powerful enough. Any ideas?
Thanks.

It is always difficult when these one-to-many situations have to be handled in BW.
Here are two approaches:
One model is to have two sets of records, one of header level and one on cost item level. The header level set of records would have the key figure(one record with 20) because it belongs there. There is an extractor for that I think it was 2LIS_08_TRTK. The cost item level set off records should not have this KF.
You can now have these two to sets of records either in one cube or in two separate cubes with multiprovider on top.
This is the clean way.
When designing the queries, keep in mind that there are multiple records (one header and many cost item records). For example you can report only on header and jump-query to the items.
Second model would be to collapse the items to the header. So instead of having three items, have only one header record and aggregate the items. This requires user participation and agreement to a design where the cost item records will not be immediately available but instead a compressed record will be. For example if you have a date, you can create first date and last date characteristics on the header record.
The exception aggregation may not actually work in all cases, I am not sure with what characteristic and what exception in particular you using.

Similar Messages

ISO: person or forum for data modeling guidance

hello -
Is there anyone here who is willing/able to advise me on the data model that my husband and I have been working on? Alternatively, can anyone suggest an alternative forum, or where I need to go to have this done professionally?
Our background is that we're both self-taught; he has a functioning database (in Approach) that we want to re-build and expand upon. I have a set of related tables in Filemaker that are semi-functional.
We're not sure if his original model is the most stable way to have built it, nor are we sure that we're expanding in the right way to encompass my tables....
I really do NOT want to pay someone to write this whole application for us - beyond the expense, we like/want to be in control.
Thank you -
Marion in Rochester

Marion
My e-mail address is in my profile, drop me a line and I'll be happy to have a look.
A few things first though. Download and install Oracle XE if you have not done so already. Let me know what SQL knowledge you have specifically Oracle DDL (Data Definition Language - Using for creating and altering database objects) and DML (Data Manipulation Language - Used for inserting, updating and deleting rows from a table).
Next send me the data model by way of what tables (and their columns), primary keys, foreign keys, constraints, indexes (if any yet) that you currently have. I will also need to know roughly how many rows you currently have in each table. Send this in any format you want (even just a text file) but not as a database.
Cheers
Ben

PowerPivot removed table replicated into the data model on refresh

Hey
I am facing the following problem which is absolutely persistent and annoying in nature. I am using a data model created with PowerPivot with connections to three different SQL servers and 25 tables. The bug is that every time I refresh my data, a table
that was initially added to the data model (and later removed) is replicated in equivalent number of tables that use this connection, which is currently around 12 tables, so I get 12 duplicates of the same unnecessary table on every refresh, named with the
name of the schema on the SQL server that is followed by a running number. Removing these from the data model on every refresh simply takes too much time on a daily basis. The additional undesired table which is created is what is defined in the SQL query
of the connection string of this connection.
I tried to solve this problem by zipping the Excel file and modifying this SQL statement present in the connection string in the connections.xml file in a way that it would not return anything, but this always leads into a corrupted workbook.
After encountering this I have managed to avoid this problem by making sure that the initial table I'm adding to the data model will remain in the model, but I really don't want to rebuild this current model. Is there any fix for this issue without
rebuilding the data model?
Thanks for all the help in advance!

I am using 64-bit Office 2013 with the recent SP1 upgrade and the included PowerPivot plug-in on a Windows 8.1 machine.
I always create the connection by using "From SQL server" then fill in the server and log in details and use a ready SQL statement that I have written by using SQL Server Management Studio to import the initial table. For all the preceding tables
using the same server and schema, I always select it from existing connections and just paste the SQL queries required for any additional tables to the "Write a query that will specify the data to import", rather than using the table import tool.
I am not sure if it could have any effect that I've been using the type connection "From SQL server" although the database is really running on Azure (there is a possibility to select From Other sources > Microsoft SQL Azure, but the functionality
seems the same).
I don't really understand what I should edit from the existing connections section. Just to clarify, apparently the Connection String parameters can be edited from PowerPivot, but not the Command Text which can be viewed from Excel Data > Connections
> Properties, but is shown in gray with a message "Some properties cannot be changed because this connection was modified using the PowerPivot add-in."
In the data model I am using two sets of identical tables, but connected to two different servers that are running a database 1:1 in structure. Initially the problem considered only the other of these, but I accidentally reproduced it by, again, editing
the SQL query in the table that was initially imported when that connection was created (PowerPivot > Design > Table Properties). Now when refreshing I get tables that are structured as in what the "Connection Text" part of the connection would
produce, which replicated for the equivalent amount of additional tables using the same connection, so now I'm getting 12 tables (the number of tables using the same connection) each named "*schemaname1* Query", "*schemaname1* Query2",
"*schemaname1* Query3" "*schemaname2* Query" and so on.
Personally I can definitely see a pattern here. If there isn't a table matching what has been specified in the "Command Text" that was described when the connection was created, then it for some reason runs this query anyway on every table that
is using the connection.

Xcode, how do you take an app from an idea to a data model, data structure, or class structure?

Hey everyone!
I'm a beginner xcoder and computer engineering sophomore and have literally spent every hour of the past few weeks reading as much as I possibly can about becoming a developer.
I've found plenty of documentation, and guides on how to do very specific things in xcode and objective-C but am still looking for more information on one topic; how do you decide which data models/structures/controllers etc to use?
I mean, you personally. I've been looking for a resource on this and have not been able to find one. I just finished Apple's iOS Developers Guide and they mention "choosing a data model" but do not describe them in much detail.
The following is what is provided in the guide:
● Choose a basic approach for your data model:
● Existing data model code—If you already have data model code written in a C-based language, you
can integrate that code directly into your iOS apps. Because iOS apps are written in Objective-C, they
work just fine with code written in other C-based languages. Of course, there is also benefit to writing
an Objective-C wrapper for any non Objective-C code.
● Custom objects data model—A custom object typically combines some simple data (strings, numbers,
dates, URLs, and so on) with the business logic needed to manage that data and ensure its consistency.
Custom objects can store a combination of scalar values and pointers to other objects. For example,
the Foundation framework defines classes for many simple data types and for storing collections of
other objects. These classes make it much easier to define your own custom objects.
● Structured data model—If your data is highly structured—that is, it lends itself to storage in a
database—use Core Data (or SQLite) to store the data. Core Data provides a simple object-oriented
model for managing your structured data. It also provides built-in support for some advanced features
like undo and iCloud. (SQLite files cannot be used in conjunction with iCloud.)
● Decide whether you need support for documents:
The job of a document is to manage your app’s in-memory data model objects and coordinate the storage
of that data in a corresponding file (or set of files) on disk. Documents normally connote files that the user
created but apps can use documents to manage non user facing files too. One big advantage of using
documents is that the UIDocument class makes interacting with iCloud and the local file system much
simpler. For apps that use Core Data to store their content, the UIManagedDocument class provides similar
support.
I suppose my question boils down to, how do you decide which structures to use? If you can provide an example of an app idea and how its implemented that would be very helpful and much appreciated!
For example, to implement the idea of an app which allows users to progress through levels of knowledge of a certain subject and rewarding them with badges and such (this is not an actual app just a whim) how would one model that?
Thanks in advance for all your help!!!

SgtChevelle wrote:
how do you decide which structures to use?
Trial and error.
I wish I had a better answer for you, but that pretty much encapsulates it. There is some, but not much, good wisdom out there, but it takes a significant amount of experience to be able to recognize it. The software development community if currently afflicted with a case of copy-and-paste-itis. And the prognosis is poor.
The solution is to be brutal to yourself and others. Focus on what you need and ignore everything else. Remember that other people have their own needs and methods and they might not be applicable to you. Apple, for example, can hire thousands of programmers, set them to coding for six months, pick the best results, and have the end-users spend their own time and monety to test it. If you don't have Apple's resources and power, think twice about adopting Apple's approach. And I am talking from a macro to a micro perspective. Apple's sample and boilerplate code is just junk. Don't assume you can't do better. You can.
Unfortunately, all this takes time and practice. You can read popular books, but never assume that anyone knows more than you do. Maybe they do and maybe they don't. It takes time to figure that out. Just do your best, ignore the naysayers, and doubt other people even more than you doubt yourself.

Data modeling dilemma for EAV oriented problems in Data Modeler

Hello,
Dealing with EAV( entity attribute value model ) oriented structure of data.
So this look like this:
Entity( Entity_Id number , Entity_Name varchar2, Entity_Desc varchar2 )
Entity that list attributes and some meta data on characteristics of attributes:
Type_Of_Attribute( Attr_Id varchar2, Type_Of_Value TOV_Domain, Unit_Of_Value varchar2 , Min_Value variant_type , Max_Value variant_Type )
Then we have actual data. Entity is described with set of attributes and their values. So aditionally to attributes on row form in Entity there are aditional attrbutes in columnar form.
Because of sparsity...
However there in columnar form the challenge or issue is type of values so domains of attributes.
For example:
weight_of_ person is number between min_number and max_number.
But another parameter for example mood_of_person is string from the domain which consists of set of strings/descpriptions.
Another possibility could be reference to some table of values ( key value ) that could be modelled as one:many relationship if put in entity Entity on row form of attributes.
But since this is attribute relate only to few intances or it is very dispersed....and for preserving table form..it was put in columnar form ..
Attribute_Of_Entity( Entity_Id, Attr_Id, value,
-- when not normalized, could be add also unit like kg or lbs or inch or piece ).
My question is on good/succesfull practice of modelling for VALUE in attribute_of_entity?
Somewhere read that some databases have feature of so-called variant type.
Guess the objective is to modell in such a way that implementation of this model is as easy as possbile in
issues like:
a) validating column oriented form during entering or updating values
b) consolidating queries when reporting
c) agregating data when grouping when grouping data and preventing non-comparable data.
So to implement value as structure/complex_type with methods or there is any other feature supporting variabilty of the data along same column in the table. So logical design that would not cause too much complexity in the relational design and table implementation and procedures are handled as much as possible on the database level?
Thank you in advance for comments, experiences, suggestions,

Hello,
EAV is rarely a good solution. Tell us about your business problem and we might be able to show you solutions that are performant/easier to maintain/...
https://www.simple-talk.com/opinion/opinion-pieces/bad-carma/
Regards
Marcus
BTW: this question should not be asked in the forum space for the tool SQL Data Modeler. Instead ask in SQL and PL/SQL or General Database Discussions

Prob in joining Query1 and Query2 in Data Model

Hi,
I m facing a prob. in joining Multiple queries
Under data model I've created 2-3 queries which I've to join internally and in my Query1 only 1 bind variable is there, for which i've created a parameter
but for Query2 and Query3 I m going to user one column value of Query1 as parameter.
When i m doing this the Xml formed returns only Query1 value and Query2 and Query3 comes as blank.
Eg.
Query1 : select deptno,dname from dept where deptno=:p_deptno <:p_deptno is a parameter created in parameter list>
Query2 : select empno,ename,mgr from emp where deptno=:deptno <where :deptno, i m expecting to come from Query1>
but it not happening
whereas my Xml comes as display below:
<DATA>
<Q2>
<Q2_ROW>
<DEPTNO>10</DEPTNO>
<DNAME>ACCOUNTING</DNAME>
</Q2_ROW>
</Q2>
<Q1 />
</DATA>
tanks in advance for replying
Regards/goutam

Personally, I have had a hard time doing what you are asking for using netui tags. I have had the same case, and asked the person in my team to just return a collection of value objects and then iterate through it without the repeater tag. To use the checkbox, I have had to use a String[].
Kunal

Two data Models in one report

Hi There,
I have created two data model for my report. The queries have no relation to each other. Is that possible to put both these in one report with same user parameters. or do u have any better suggestion to do this.
For Example:
select count(*) from (select name "Worker" from person
where start_date between (:P_1) and (:P_2)
select count(*) from (select name "ADMIN PERSON" from admin
where start_date between (:P_1) and (:P_2)
Thanks

Hi Jagjit,
I created one report with 2 SQL queries:
select count(*) from employees where department_id < :P_1
and
select count(*) from departments where department_id < :P_1
And it worked fine. So your report should be OK. By the way, a report has just one "Data Model". It is possible to have 2 or more "Queries" in the data model.
Navneet.

Inheritance in OPA data model

Hi all,
I have a problem which OPM does not seem to handle well, but maybe I am lacking knowledge concerning some functionality. I am using a client patched 10.1 version of OPM.
Situation:
- I have an attribute in Global, which states the possibility to export an entitlement. This attribute is deducted using multiple compositions of conditions on both "child" level and "applicant" level. These are both entities in my data model.
- However, some of the conditions are the generic for both roles. Therefore, what I really want to do is check attributes on "person" level and relate these to "the child" and to "the applicant".
- Now, I've created an entity "the person" with a relation to "the child" and a relation to "the applicant".
This raises an issue with the For/ForAll operator
Issue:
- To use the "For" operator, a -to-one relationship is needed. However, I can have two persons of which one is a child and one is an applicant. So, I need a - to-many relationship for person (from Global)
- If I use the "ForAll" operator to 'work around' this problem, the goal attribute will stay inconclusive as the relationship from person 1 to the child is known, but from person 2 to the child in unknown (and vice versa for the applicant)
Question:
It seems to me that this is an issue of inheritance which OPM cannot handle. I am wondering:
- has anyone dealt with this problem and/or does anyone have a solution?
- is it likely that the entity containment functionality of OPM 10.2 + will be able to solve my issue?
Thanks & regards, Els

Given that I don’t know the details of your source material, and I don’t know Dutch, perhaps the best option is if I show you how to get a simple inferred relationship set up and working. Hopefully then you’ll see what it’s doing and know how to set it up for your own rulebase.
1. Create a new empty test rulebase.
2. Add a Properties file. Add a regular one-to-many containment relationship from Global to ‘the person’.
3. From within the Properties file, have Global selected and in the right hand pane select the Relationships tab.
4. Right-click in an empty space in the right hand pane and select ‘New Relationship’. Use these settings:
- Source: Global (This will already be set, and will be read-only. If it isn’t already set to Global, then you didn’t do Step 3.)
- Target: the person
- Relationship type: Inferred (many-to-many)
- Text: the adults
5. Save the Properties file.
6. Create a Word rule doc.
7. Add a membership rule for the inferred relationship. A membership rule specifies the logic used to decide which instances are members of the inferred relationship. The parts in italics below are just examples of what the red configuration text will look like when the rule is compiled.
+[IsMemberOf(“person”,adults)]+ the person is a member of the adults if
+[p1 >= 18]+ the person's age >= 18
In my example, I’m just basing it on age. It could be based on just about anything. Try to name your inferred relationship appropriately. I called it “the adults” since that’s what the group is. If I needed to have a group of people >= 18 years and who are female, then I’d call it something like ‘the female adults’, and obviously I’d include gender in the membership rule.
8. Add some simple entity calculation rule such as these:
the number of adults in the group = InstanceCount(the adults)
the total amount of savings of the adults in the group = InstanceSum(the adults, the person's savings amount)
9. Build and Debug. Work in the Data tab, not the OWD tab. You’ll be able to see more detail about what’s going on if in the Data tab.
10. Add three instances of ‘the person’. Make two people older than 18 years, and one person younger than 18 years. Give each of them a different savings amount.
11. Look at the Global results and you will see that the InstanceCount rule calculated ‘2’ and the InstanceSum rule only added up the savings from the subset of people who are adults.
My general advice on this is:
If the logic you need to do over subsets of entity instances is relatively simple, and can be easily accommodated by existing Instance functions, then don't bother with inferred relationships. Just set up the regular containment relationship and use the existing entity functions. Here are few examples of less complex entity calculations which can easily be handled without inferred relationships:
- count the number of adults
- calculate the total income of all household members who are over 25 years
- find the age of the youngest male child
So my example rulebase above is actually one for which I wouldn’t use inferred relationships if that was all I needed it for. I just wanted to pick a simple example to explain the concept. To do the example above without inferred relationships, you’d just need to use InstanceCountIf and InstanceSumIf and put the conditional logic in each calculation rule.
If the logic you need to do over subsets of entity instances is much more complex and either it's not possible without inferred relationships, or it's just easier/more concise with inferred relationships, then add inferred relationships.
Cheers,
Jasmine

Performance impacts of attributes versus entities in data model design

I'm trying to understand the performance implications of two possible data model designs.
Here's my entity structure:
global > the person > the account > the option
Typically at runtime I instantiate one person, one account, and five option 's.
There are various amounts determined by the person's age that need to be assigned to the correct option.
Here are my two designs:
Design one
attributes on the person entity:
the person's age
the person's option 1 amount
the person's option 2 amount
the person's option 3 amount
the person's option 4 amount
the person's option 5 amount
attributes on the option endity:
the option's amount
supporting rule table:
the option's amount =
the person's option 1 amount if the option is number 1
the person's option 2 amount if the option is number 2
the person's option 3 amount if the option is number 3
the person's option 4 amount if the option is number 4
the person's option 5 amount if the option is number 5
Design two
attributes on the person entity:
the person's age
attributes on the option entity:
the option's amount
the option's option 1 amount
the option's option 2 amount
the option's option 3 amount
the option's option 4 amount
the option's option 5 amount
supporting rule table:
the option's amount =
the option's option 1 amount if the option is number 1
the option's option 2 amount if the option is number 2
the option's option 3 amount if the option is number 3
the option's option 4 amount if the option is number 4
the option's option 5 amount if the option is number 5
Given the two designs, I can see what looks like an advantage for Design one in that at runtime you have less attributes (6 on the one pension member + 1 on each of 5 options =11) than Design two (1 on the one pension member + 6 on each of 5 options = 31), but I'm not sure. An advantage for Design two might be that the algorithm has to do less traversing of the entity structure: the supporting rule table finds everything for the option's amount on the option.
Either way there is a rule table to determine the amounts:
Design one
the person's option 1 amount =
2 if the person's age = 10
5 if the person's age = 11
7 if the person's age = 12, etc.
Design two
the option's option 1 amount =
2 if the person's age = 10
5 if the person's age = 11
7 if the person's age = 12, etc.
Here it looks like the rulebase would have to do more traversing of the entity structure for Design two.
Which design is going to have better performance with a large amount of rules, or would it make a difference at all?

Hi!
In our experience you only need to think about things like this if you were dealing with 100s or 1000s of instances (typically via ODS). As you have a very low number, the differences will be negligible, and you should (usually) go with the solution which is the most similar to the source material or the business user's understanding. I also assume this is an OWD project? Which can be even better, since the inferencing is done incrementally when new data is added to the rulebase, rather than in one "big bang" like ODS.
It looks like design 1 is the simplest to understand and explain. I'm just wondering why you need the option entity at all, since it seems like a to-one relationship? So the person can only have one option 1 amount, one option 2 amount etc, and there are only ever going to be (up to) 5 options...is that assumption correct? If so, you could just keep these as attributes on the person level without the need for instances. If there are other requirements for an option instance then of course, use them, but given the information here, the option entity doesnt seem to be needed. That would be the fastest of all :-)
Either way, as the number of instances is so low, you should have nothing to worry about in terms of performance.
Hope this helps! Write back if you have any more info / questions.
Cheers,
Ben

Logical data model

hi
I am currently making a white paper on rdbms and logical data models. Can anyone point from where can I get a logical data model for the telecommunication industry for data warehousing purposes ???
regards
Kunal Choksi

Instead of using exploit like that, I prefer to find a way to represent reality more generally. In the following model for example it is possible to specify also the reason for the end of a marriage ( divorce,death of partner, annulment, alimony ) in the right table.
CREATE TABLE PERSONS (
     PERSON_ID NUMBER PRIMARY KEY,
CREATE TABLE MARRIAGES (
     MARRIAGE_ID NUMBER PRIMARY KEY,
     BEGIN_DATE DATE NOT NULL,
CREATE TABLE OLD_MARRIAGES (
     MARRIAGE_ID PRIMARY KEY,
     CONSTRAINT DIVORCES_MARRIAGE_FK
          FOREIGN KEY (MARRIAGE_ID) REFERENCES MARRIAGES,
     CAUSE_OF_END VARCHAR2(N) NOT NULL, --<--- DIVORCE,DEATH,...WHATEVER
     END_DATE DATE NOT NULL,
CREATE TABLE ACT_MARRIAGES_RELATIONS (
     PERSON_ID NUMBER NOT NULL,
     CONSTRAINT ACT_MARRIAGES_PERSON_FK
          FOREIGN KEY (PERSON_ID) REFERENCES PERSONS,
     MARRIAGE_ID NUMBER NOT NULL,
     CONSTRAINT ACT_MARRIAGES_MARRIAGE_FK
          FOREIGN KEY (MARRIAGE_ID) REFERENCES MARRIAGES,
     CONSTRAINT ACT_MARRIAGES_PERSON_UNQ
          UNIQUE (PERSON_ID)
CREATE TABLE OLD_MARRIAGES_RELATIONS (
     PERSON_ID NUMBER NOT NULL,
     CONSTRAINT OLD_MARRIAGES_PERSON_FK
          FOREIGN KEY (PERSON_ID) REFERENCES PERSONS,
     MARRIAGE_ID NUMBER NOT NULL,
     CONSTRAINT OLD_MARRIAGES_MARRIAGE_FK
          FOREIGN KEY (MARRIAGE_ID) REFERENCES DIVORCES
/The two tables to represent marriage_relations (actual and old ones) are there only because with this choice it is possible to specify a unique constraint on actual marriages that avoids the same person to be related in different marriages.
Bye Alessandro

How to create an exclusive relationship in IE Data Model

Hello Experts,
How can I specify exclusive relationships in the IE Data Model? I have a PERSON and a ORGANIZATION entity. Both have a relationship to an ADDRESS entity. The ADDRESS entity can only have a relationship to either PERSON or ORGANIZATION. How is this situation modeled in the IE Data Model?
Thank you,
Carsten

Relationships in the IE Data Model method are between only 2 entities. There is no way to directly model a three-way relationship that you are trying to use. The alternatives for modeling it in the IE method would be to use a generalization structure on one end or the other. You could generalize Person and Org into a higher level concept (typically called Legal Party or just Party) and draw the relationship from the new Party entity to Address. Or, you could subtype Address as either a Person Address or and Organization Address and draw relationships from the new subtypes to Person and Organization respectivley.
You could also choose to just annotate it on the diagram using either text or a graphic object.

Including table and column comment in the Data Modeler

Hi all,
I used Oracle's SQL Developer Data Modeler (Version 3.0.0.665) and created a data model for my project. I e-mailed a PDF format of the data model to our Systems Analyst. She asked if I could re-create the data model and include table and column comments. Is this a possibility and if so how is this done?
Thank you for your input,
Seyed

Hi Kent,
Using the information you provided and Oracle’s Working with SQL Developer Modeler Reporting I did the following:
1) Created a Reporting Schema User
1.1) Using my Oracle 10g Personal Edition, I created a new user and gave him DBA administrative privileges
2) Exported Relational Design to Reporting Schema
2.1) Opened the Relational Design
2.2) Exported it to the Reporting Schema. Note, I never got a message ‘Design has been exported successfully’.
3) Reviewed the Report Results
I think exporting the relational design was not successful, and didn’t get any error messages. Had step 2 completed successfully, I would have reviewed the Report Results in SQL Developer. By the way, I know I have marked this topic as closed, but would like to learn your method too.
Thank you for your help,
Seyed

Data Modeler Save and Save As not working

I am using the latest SQL Developer (Version 3.0.04 Build MAIN-04.34). Within it I am trying to use the Data Modeler. In the Browser, under Designs, Untitled_1, Relational_1 I can add tables and arrange them in a diagram.
It is not possible to save it.
Going File > Data Modeler > Save I am presented with a 'Save Design' window with a 'File name' of 'file:/' and a 'File type' of 'dmd' and 'dmdz'. I have tried numerous alternatives to save my diagram. I must remove the literal 'file:/'. I have tried 'test', 'test.dmd', 'test.dmdz'. I have tried the default location of 'C:', I have tried the directory in which I wish to store the diagram. To no avail.
Does anyone have any ideas as to what I need to do to save this diagram?
David
Edited by: djmartin_ACC on 8/06/2011 19:12
Edited by: djmartin_ACC on 14/06/2011 16:12

K,
I pointed the Default Designs Directory to a directory on my PC (C:\David's stuff) but when I press 'OK' the window does not close. I tried different directory names - C:\With space's, C:\Without_spaces, and C:\Withsmal. It doesn't matter which I use the window will not close.
When I use the same name in each of the five slots, press 'OK', then 'Cancel', and reopen the Preferences window all but Default System Types Directory contain the value I supplied. Is this other directory something special?
Once I do have data in any of the slots, the window will not close when 'OK' is pressed.
I closed and reopened SQL Developer and the four previously populated Directory slots are empty again.
I have tried this with MyEclipse running and not running without any difference in behaviour. The only other software I am running is MS Word, Firefox, and Citrix.
Any ideas will be gratefully received. I will be trying the software on my personal laptop this weekend and see what differences I find then.
David

Represent interfaces in data model

How can a Java interface with its own properties be represented in a data model? It would be like multiple inheritance for implementing classes from a data perspective, but in some data modeling it says that multiple inheritance is an illegal data modeling construct...
How do you go about representing interfaces? For example, many classes that are in their own inheritance hierarchies but all implement an interface with getters and setters for a particular persistent property?
Thanks.

How can a Java interface with its own properties be
represented in a data model? It can't.
It would be like
multiple inheritance for implementing classes from a
data perspective, My experience says that is a bad idea. For version one it seems like employee should be a child of person. And then for version two you have to add contractors, and volunteers and even companies (as an entity that produces work and gets paid an hourly rate) and then the inheritence model completely fails.
How do you go about representing interfaces? For
example, many classes that are in their own
inheritance hierarchies but all implement an
interface with getters and setters for a particular
persistent property?In a modeling tool I might have one page that lists impementations of some interfaces.
On another page I just show relationships with the interfaces (no implementations are shown.)
A data object itself should not be an interface.

Oracle Data Modeler - Impact Analysis option

Hi
I am using Oracle Data Modeler 3.1.0683 and reversed engineering my existing relational models to logical models. I have 3 relational models and reverse engineering it to 1 logical model.
In logical model under enity's propoerties -> impact analysis how do I add which relational table the logical entity depends on? For example in relational models i have table Class, Student, teacher in 3 separate relation model. Logical i created entity Person which depends on table Student from relational model 1, and teacher from relational model 2, I want to view(add) these tables under "Impact Analysis".
The help window says
<quote>
+"Impact Analysis+
+Enables you to view and specify information to be used by Oracle Warehouse Builder for impact analysis."+
</quote>
Though i couldnt figure out where to specify?
Thanks in advance.
Regards
Lahoria

So any suggestions how can I bring those table ( as i mentioned in original post) to show up in Impact AnalysisIf your entity is result of reverse engineering from relational model then you can find related table under mappings. The same if you engineer logical model to relational model.
If you start from column then you can see related attribute in logical model and usage in data flow diagrams and dimensional models
Philip

IDM person centric data model

Similar Messages

Maybe you are looking for