ADF-Master detail-Foreign key generated By Trigger won't propaget to Detail

Hi All,
We have Master-Detail Table where Master table key is generated by DB.
And this key act as Foreign key in detail table.When we Creates Master Table records and commit it .It gets saved correctly But when we navigate to Create Detail record (Cretae button is taken from Detail) It opens in Create mode but does n't poppulate Foreign Key.
Can anybody plz explain..
Regards
Yogesh

Hi Frank,
Thanks for your reply.I don't know "the ADF Business Components tester "
what is this ?
I was able to solve my problem by making "Refresh after insert " Check box selected in Entity object.Now it is generating Master Key and also i am getting it in Detail.
But now problem is, Can we make details record in insert mode by 'Create opration' under Master View.My requirment is insert two records in detail table in background while inserting record in master.Where relationship is maintained by foreign key which generated by trigger.
I want master and detail create form on same page where i will make details from Rendering False i.e both should be in Create mode (Accesser should not retrive record).
In Short
ADF-BC Master Detail - Detail Record insert in Back ground on the same page
Thanks in Adv
RHY

Similar Messages

PRIMARY KEY(MASTER)를 REFERENCE하는 FOREIGN KEY 찾는 SQL

제품 : ORACLE SERVER
작성날짜 : 2004-03-12
PRIMARY KEY(MASTER)를 REFERENCE하는 FOREIGN KEY 찾는 SQL
========================================================
$sqlplus sys/manager(SYS user 로 login 함)
sql> select c.name constraint_name
from dba_objects a,
cdef$ b,
con$ c
where a.object_name = 'TABLE_NAME'
and a.object_id = b.robj#
and b.con# = c.con#
/

Hello again,
May be I was not clear enough.
Scenario 1: We use the master-detail form as is with the default oolbar. In this case, the user can insert the detail records one by one without needing the primary-foreign key value since this is handled by default.
Once we save the form (commit_form), I use the pre-insert trigger to get the master block primary key generated from the sequence and since the detail block key is copied from this value, both are saved correctly and it is the end of the story.
Scenario 2: As explained in the initial post, the user will populate the detail records one by one by clicking on the -INSERT DETAIL- button and hence has a window where he can insert the detail info and then be brought back to the master-detail form every time he enters a new detail record.
The problem here is that I can't generate the primary key for the master block since the client has the following requirement:
The user can always change his mind and not complete, meaning save the form, his process
As such, the key should be generated in the last step before Commit.

Entity bean with primary key generated by trigger

Hi,
We have a table(oracle) with one column as primary key,
but the primary key is generated by trigger every time
a new row is inserted into this table, inside the trigger,
it uses oracle sequence to get the next val.
If we want to use entity bean with it, what should we specify, it's not application-managed primay key, it's
not auto-generated primary key either. How can we resolve
it without change the database part.
Any thought is appreciated.
Thanks
afang

The code is already there with JDBC call inserting
into the table, the inserting trigger then will generate
sequence key and being inserted into primary key column.
Now wondering if it's possible to change the code to use entity bean but without modifying the trigger (since it contains other business logics).

Why are no foreign keys generated with inheritance?

I have a very simple ORM strutcure that I am trying to create with JPA, using inheritance. The two tables get created, but there is not PK-FK relational link between them generated. I know they CAN be generated, because I have other relationships (not using inheritance) where it works.
Could someone please look at these listings and tell me what I am doing wrong? Thank you!
I have this property set in persistence.xml:
<property name="kodo.jdbc.MappingDefaults" value="ForeignKeyDeleteAction=restrict"/>
Here's the base class:
@Entity(name = "Sensor")
@Table(name = "SensorRecord")
@Inheritance(strategy = InheritanceType.JOINED)
@DiscriminatorColumn(name = "SubType", length = 100)
public abstract class Sensor {
    @Id
    @GeneratedValue
    @Column(name = "RecordId")
    private long recordId;
    //@Basic
    @Temporal(TemporalType.TIMESTAMP)
    @Column(name = "Timestamp")
    private Date timestamp;
    /* JPA uses a version field in your entity to detect concurrent
       modifications to the same datastore record.
       The version field must be an integral type ( int, Long, etc) or a
       java.sql.Timestamp. You should consider version fields immutable. */
    @Version
    private int version;
Here's the derived class:
@Entity(name = "Altimeter")
@Table(name = "AltimeterRecord")
@DiscriminatorValue("Altimeter")
public class Altimeter extends Sensor {
    @Basic
    @Column(name = "Altitude")
    private int altitude;
And finally, here's the (redundant) orm.xml:
<entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm orm_1_0.xsd"
    version="1.0">

<access-type>FIELD</access-type>
<entity class="navdemo.persistence.Sensor" name="Sensor" access="PROPERTY">
    <table name="SensorRecord"/>
    <inheritance strategy="JOINED"/>
    <discriminator-column name="SubType" length="100" discriminator-type="STRING"/>
    <attributes>
      <id name="recordId">
        <column name="RecordId" column-definition="BIGINT"/>
        <generated-value strategy="AUTO"/>
      </id>
      <temporal value="TIMESTAMP">
        <column name="Timestamp"/>
      </temporal>
      <version name="version"/>
    </attributes>
</entity>
<entity class="navdemo.persistence.Altimeter" name="Altimeter" access="PROPERTY">
    <table name="AltimeterRecord"/>
    <discriminator-value>Altimeter</discriminator-value>
    <attributes>
      <basic name="altitude">
         <column name="Altitude"/>
      </basic>
    </attributes>
</entity>
</entity-mappings>

Hi,
well I suggest to use the InputMap/ActionMap approach.
Something like this should work:
    private void installMyActions() {
        CloseAction closeAction = new CloseAction("closeAction");
        installMyAction(closeAction, KeyStroke.getKeyStroke("ESC"));
    private void installMyAction(AbstractAction action, KeyStroke keyStroke) {
        getInputMap(JComponent.WHEN_IN_FOCUSED_WINDOW).put(keyStroke, action.getValue(Action.NAME));
        getActionMap().put(action.getValue(Action.NAME), action);
    class CloseAction extends AbstractAction {
        public CloseAction(String name) {
            super(name);
        public void actionPerformed(ActionEvent e) {
            dialog.setVisible(false);
    }Hope that helps,
Michael

Master-detail with auto-generated primary key(master)

Hello,
I have the following master-detail setup:
Master - block A primary key is: codeA
Detail - block B
codeA is genrated only at commit time and is obtained from a sequence.
User needs to add detail records. This is easy to do since he has to click on the insert icon on the toolbar. At commit time, use commit_form.
Prob: the requirements as asked by the client is to add a button (which we will label INSERT DETAIL). When the user click on the button, it opens a window where he can enter the detail info then click on save. This should bring him back to the master-detail form and the record in the detail block is inserted.
What is the problem here ? since the detail block has the foreign key tied to the master primary key, the window-form (with the call_form) that we opened for the detail entry won't be able to save since at this point we still have not assigned a value for the primary key (and hence a value for the foreign key).
Possible Suggestions:
-Use a temp database table to hold the detail record from the second form and use it to transfer values to the detail record in the master-detail
-Use a global record group
-We can't use parameter list to pass back these values.
So my question is:
What would be the most efficient way to have an insert button on the detail block that would allow the user to have a pop up where he can insert his values and then be brought back to the master-detail.
Thanks.

Hello again,
May be I was not clear enough.
Scenario 1: We use the master-detail form as is with the default oolbar. In this case, the user can insert the detail records one by one without needing the primary-foreign key value since this is handled by default.
Once we save the form (commit_form), I use the pre-insert trigger to get the master block primary key generated from the sequence and since the detail block key is copied from this value, both are saved correctly and it is the end of the story.
Scenario 2: As explained in the initial post, the user will populate the detail records one by one by clicking on the -INSERT DETAIL- button and hence has a window where he can insert the detail info and then be brought back to the master-detail form every time he enters a new detail record.
The problem here is that I can't generate the primary key for the master block since the client has the following requirement:
The user can always change his mind and not complete, meaning save the form, his process
As such, the key should be generated in the last step before Commit.

Catch foreign key violations in the model, not the database

I must do something wrong, when I want to delete a master that still has details, the application will let me, but the database returns an FK violation error when the commit button is pushed. The association is in the model, there is no viewlink though.
Why doesn't the framework check this before the database does? And how could I make the message more userfriendly? My users have no idea what it means if BLABLA_FK is violated
Thanks in advance

I might have the source of this problem. I have a table that has 2 foreign keys to the same other table. In my RowImpl I get duplicate case labels when I create both viewlinks because the final int gets the name of the referring table.
Doesn't ADF support 2 foreign keys to the same table?
Update: a testcase showed me that I chose the same name for the accessors of 2 different viewlinks, so that was not the problem.
Message was edited by:
Wendy Tromp

Primary key foreign key remove problem

hi expretrs,
I create 5 tables in ddic.
1. zpr_cmp Company Master
2. zpr_dpt Department Master
3. zpr_dsg Designation Master
4. zpr_emp Employee master.
5. zpr_slm Salary Master.
Foreign key reference in zpr_emp from table 1,2 and 3 created and
table zpr_emp has
cmpcd, Company Code
empcd, Employee Code
dptcd , Department Code
dsgcd Designation Code
as key fields.
I have upload data and create module pool and reports.
My problem that hr person say that we want to change deptcd/dsgcd of employee (zpr_emp) and
dptcd and dsgcd is as key fields in zpr_emp when i change the table zpr_emp and remove
two key fields dptcd/dsgcd and active error display.
I also try with se14 (Activate and Adjust database) but error still.
how can i remove key field from zpr_emp and active table without loss data and without any change of
module pool/reports
pl. help

Diagnosis
ZPR_EMP table is defined as a check table. For reasons of consistency, changes to the primary key of the table are not allowed.
Procedure
If it is essential that you change the primary key, you must delete the relevant foreign keys. Refer to the where-used list to find all tables containing a field that is checked against this table. Delete the foreign keys for these fields.
If necessary, maintain the deleted foreign keys again.
Value table - It's a field in a domain it helps in domain level data validation.
Check table - unlike value table it helps in feild level data validation.
The relational data model contains not only tables, but also relationships between tables. These relationships are defined in the ABAP/4 Dictionary by foreign keys. An important function of foreign keys is to support data integrity in the relational data model. Foreign key fields may assume only those values allowed by the check table, in other words, values occurring in the primary key of the check table.
A foreign key provides a link between two tables, for eg.,T1 and T2 by including a reference in table T1 to the primary key of table T2. For this purpose, Foreign key fields assigned to the primary key fields of T2 are included in T1. Table T1, which is the one being checked, is called a foreign key table, and table T2 is called a check table. The terms dependent (foreign key) table and referenced (check) table are also used.
VALUE TABLE:If the domain of the check field has a value table, this is proposed by the system as check table in the foreign field maintenance. The key fields of the value table are in this case assigned fields of the foreign key table with the same domain. These fields may assume only those values allowed by the value table.
The value range of the domain can be defined by specifying value table.All table fields referring to this domain can then be checked against the corresponding field of this value table.In order the check can be executed, a foreign key must be defined for the value table.

FOREIGN KEY CONSTRAINT

HI GUYS
I DID THE FOLL
CREATE TABLE MASTER(EMPNO NUMBER PRIMARY KEY,
ENAME VARCHAR2(12));
CREATE TABLE CHILD(EMPNO NUMBER);
ALTER TABLE CHILD ADD CONSTRAINT FOREIGN KEY REFERNCES MASTER(EMPNO)
NOW WHEN I DOTHE ABOVE AND THE DO DESC CHILD
I GET THE FOLL
EMPNO NUMBER
ENAME VARCHAR2(12)
KEY NUMBER
WHAT IS THIS KEY COLUMN ? WHY IS IT COMING
KINDLY CLARIFY

Interesting.
The correct syntax to add a FK constraint is:
ALTER TABLE child ADD CONSTRAINT
   FOREIGN KEY (empno) REFERENCES master (empno);I can replicate your behaviour in 9.2.0.6, and in 8.1.7.4. It appears that in the absence of a column list in parens, Oracle takes the word after FOREIGN and adds a column with that name and the appropriate data type to the table and uses that in the FK.
SQL> CREATE TABLE master (empno NUMBER PRIMARY KEY,
2                       ename VARCHAR2(12));
Table created.
SQL> CREATE TABLE child (empno NUMBER);
Table created.
SQL> ALTER TABLE child ADD CONSTRAINT
2     FOREIGN new_col REFERENCES master (empno);
Table altered.
SQL> desc child
Name                                      Null?    Type
EMPNO                                              NUMBER
NEW_COL                                            NUMBERJust to show that the constraint is enforced:
SQL> INSERT INTO child VALUES(1,1);
INSERT INTO child VALUES(1,1)
ERROR at line 1:
ORA-02291: integrity constraint (OPS$ORACLE.SYS_C0070911) violated -
parent key not foundBut, this only works when there is no KEY keyword:
SQL> DROP TABLE child;
Table dropped.
SQL> CREATE TABLE child (empno NUMBER);
Table created.
SQL> ALTER TABLE child ADD CONSTRAINT
2     FOREIGN KEY new_col REFERENCES master (empno);
   FOREIGN KEY new_col REFERENCES master (empno)
ERROR at line 2:
ORA-00902: invalid datatypeOn a fast scan of the documentation I don't see where this behaviour is documented, and I have certainly never seen this before. Anyone out there have any thoughts?
John

Update primary key thats also a foreign key in another table

Hi Developers,
I need to update the primary key for a record but it's also the foreign key in another table.
Example,
Table 1 Details
Name : Parent_Table
Columns : ID, Name, Age
Primary Key : ID
Table 2 Details
Name : Child_Table
Columns : ID, Parent_ID, Name, Age
Primary Key : ID
Foreign Key : Parent_ID (Primary Key in Parent_Table)
Parent_Table
ID Name Age
1001 Sam 26
1002 George 25
Child_Table
ID Parent_ID Name Age
1010 1001 Sam 26
1020 1002 George 25
Now I want to update ID (1001) in Parent_table as 2001 and also, I want to update Parent_ID (1001) in Child_Table as 2001.
How we will write the java code to update these columns.
Thanks in advance.

dcminter wrote:
If you're looking at changing the primary keys in your data then there's probably something wrong with your data structure.Depends how you feel about business primary keys versus surrogates. Personally I prefer the latter so I'm with you in theory. In practice, however, a DB that uses a business PK may well find that it's a legitimate use case to change the key value (but then that's why I like surrogates in the first place!)Primary keys should not have meaning.

Foreign key validation while creating master/detail record in document mode

I am creating master/detail records in the document mode. And I am generating the master primary key in the create() method of the master Entity Object. Now I valdate the foreign key in the detail Entity Object's validateEntity() method by doing a query to the master table through some View Object.
But since the master record has not yet been posted (since it hasn't been committed) to the database, this query does not return any record and the validation fails in detail object.
And thus the create fails.
Please let me know if this is the right approach for doing this. If so where I am going wrong? Else please let me know if there are any better approach to do this.
Kunal

Kunal:
Use a code snippet like the following:
--- Assuming you're in the detail EO's create method ---
oracle.jbo.server.EntityDefImpl eDef = oracle.jbo.server.EntityDefImpl.findDefObject(<package-qualified-name-of-the-master-Entity-Object>);
oracle.jbo.Row masterRow = eDef.findByPrimaryKey(this.getDBTransaction(), <foreign-key>);
If the row does not exist, masterRow will be null.
findByPrimaryKey first checks the entity cache (which will include your new master row(s)) and then go out to database (if it's not in cache).
Thanks.
Sung

Master-Detail Forms (Populating a Foreign Key Automatically)

Master-Detail Form
When inserting a MD Form, the Master ID (e.g. Deptno,the Primary Key) is generated.
How is it possible for this also to be generated in the Detail Form (as the Foreign Key)? The requirement is for the foreign key to be populated automatically.
Any help would be much appreciated.
Thanks.

This item is discussed earlier in this group.
It's solved in version 3.0.8
Regards,
Anna

Master detail without foreign key

Hi.
I would like to know whether it is possible in JDeveloper to have a master-detail form for two tables that do not have a phisical foreign key constraint (they do have a logical one, though)?
I tried creating an Association between the two Entities, but I do not see any effect.

This should work without dependency on the database having the relation defined.
Are you using ADF Business Components?
If so can you detail what you did and what is the behavior you see?
Also remember that you'll need to set the link at the view level also.

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?

How to fetch column data using foreign key in adf table ?

I have created a adf table using a view that has a group id and user id column. I want to display the user name ( from user table) and group name from group table. I had created view links to the corresponding tables from the user_group view ( whose iterator is used to render the table).
It sort of works. I dragged the user name from the embedded user iterator in user_group iterator. It does find the correct user name but if I have more than one row, it displays the user name of the last row user in all rows !
Is there a solution to this problem ?

Well, I saw in the view query for the association view ( for Many-Many) that the SQL already had the joins with the two ( master) tables to the association table. So I went ahead and added the descriptive columns to the select clause. Then the selected columns showed up in the attribute list by themselves ( without my intervention). So far so good.
Then I recreated the adf table attribute by dragging these newly selected attribute to the page. I still see that the value of the attribute is the same in all the rows - this time it is the value for the FIRST row. It doesn't correspond to the foreign key for that particular row.
IS THIS A BUG ? Has anyone else ever done this ?

Subquery in IF statement in trigger, without using foreign keys

Hello,
I'm investigating ways of writing a subquery in an IF statement, which is placed inside a trigger.
I wanna write smth like IF (:new.jazz not in (select goldies from T where ... )) etc. I don't know whether the fact that the IF is in a trigger adds some additional restrictions. (Does it?)
So far I found the solution described here: SubQuery Comparison in If Statement which I find a bit tacky, I could have the 'cooleststarinthegalaxy' instead of 1 and seems you need to do extra light, but still extra lifting.
I also read about the possibility of using MERGE, which I'm currently researching.
Is there any other way?
Thanks
Edited by: BluShadow on 14-Nov-2012 13:37
fixed link
Edite by me: the question is how (if possible) to do this without a foreign key.
Edited by: questioningq12 on Nov 14, 2012 6:11 AM
Edited by: questioningq12 on Nov 14, 2012 6:13 AM

Hi,
questioningq12 wrote:
Say I have tables A(namea varchar(10)), B(nameb varchar(10)), and B contains tuples ('1stname','2ndname').
I wrote a trigger before insertion, for each row, on table A. For a tuple t to be inserted, it should check whether t.namea is in the set of values nameb from B.
E.g., INSERT INTO A VALUES('1stname') should work. But INSERT INTO A VALUES ('3rdname') should fail. You can use a foreign key constraint for that.
If the tables already exist, and b.nameb is declared as UNIQUE (or PRIMARY KEY), then you can say:
ALTER TABLE a
    ADD CONSTRAINT     a_namea_fk
    FOREIGN KEY (namea)
    REFERENCES b (nameb)
;If you had a situation where you really needed to query a table in PL/SQL, and you weren't sure if the query would find anything, you could put the query in its own BEGIN ... EXCEPTION block, and test for NO_DATA_FOUND.
If you're just checking to see if a row exists or not, you can always write a query that is guaranteed to return exactly 1 row, like this:
BEGIN
    SELECT COUNT (*)
    INTO    x
    FROM    b
    WHERE   nameb = :NEW.namea
    AND         ROWNUM = 1;
    IF x = 0
    THEN
        ...        -- print msgs, raise exceptions etc
    END IF;
END;Edited by: Frank Kulash on Nov 14, 2012 9:22 AM
Added example

ADF-Master detail-Foreign key generated By Trigger won't propaget to Detail

Similar Messages

Maybe you are looking for