Service Virtualization

 View Only
  • 1.  Control Functions and sequence of tables during publish

    Posted Dec 08, 2016 02:51 AM

    Hi,

     

    I have two issues

     

    1. I have two tables one is employee and other is salary table as below 

     

    Employee table

    empno    empname  salary

    1001        satish         500

    1002        kumar         200

    1003        enni            100

    1004        Ishanth       500

    1005        Yashdeep   100

    1006        Yuvaraj       500

    Salary table                  Out put to be 

    empno                           empno    

                                            1001        

                                            1004        

                                            1006       

     

    So from above, i have to fill salary table with empno from employee table whereever salary =500.

     

    2. Is there any way to change the sequence of tables during publish to target, because one of my tables should go in a sequence.

     

    Please anyone help me on my queries.

     

    Thanks in advance

     

     

    Regards,

    Satish



  • 2.  Re: Control Functions and sequence of tables during publish

    Posted Dec 08, 2016 04:17 PM

    Hi Satish, 

     

    We are currently researching this issue and will reply soon. 

     

    Best regards,

    Taylor



  • 3.  Re: Control Functions and sequence of tables during publish
    Best Answer

    Posted Dec 12, 2016 11:27 AM

    Hi Satish,

     

    For your second query, if you define the right PK-FK relationship constraints in Datamaker, or in the database, that is, if the parent table PK is correctly associated with the child-table FK, then Datamaker will calculate the load order based on those relationships. That will ensure that the publish sequence is as expected.

     

    Thanks,

    Sameer



  • 4.  Re: Control Functions and sequence of tables during publish

    Posted Dec 27, 2016 02:27 AM

    Thanks sameer, that resolves my second issue. :-)