Skip to Main Content

New to Java

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

enter value by the user

3776704Sep 5 2018 — edited Sep 12 2018

HI,

How use nextInt as input method using jdevloper?

I cant not enter value after run the java program?

Comments

Gianni Ceresa

Honestly for me it sounds "obvious" that the "keep it stupid simple" approach is the one to use.

All the 3 have different meanings, provide different answers for different requirements.

For a "standard" outer join you definitely must start by the one in the Business model diagram, when you draw the join between Fact and Dim, that's a standard simple outer join between a fact a dimension.

This is also the easiest to maintain.

If you start playing with LTS I would say you must a real need and model built to work in that way.

Just for the example: adding you dim in the fact LTS => your dimension is into the Fact logical table, you don't have a dimension anymore. Without a dimension OBIEE will not validate your model.

With the opposite you are bringing fact columns into the dimension, if you don't add at least a column of the fact table source into the logical table of the dimension you have a warning.

Both these solutions are not clean, generate warning during the consistency check and are a perfect source of huge issues in the future when you are going to expand your model.

PS: do we agree you must not have a single warning in your RPD, right? (not that it doesn't work with warnings, but doings things right now it's the best way to avoid problems tomorrow)

1 - 1
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 10 2018
Added on Sep 5 2018
3 comments
488 views