Another strange issue with the data generator:
I have two parent tables, A and B. They do not depend on each other, but have the SAME dependencies on two other tables.
I have several child tables. Some of the children depend on A, and some on B, and some on both. For tables that depend on A, I can set A.id as the master for the A_id field, and there are no problems generating data (I generate A.id from a simple sequence(1,1)). Tables that depend on B.id cannot be generated by the data generator. I have no idea why. The constraints and relationships are the same. Any tips/detailed instructions?
Sometimes the ordering matters: If I have the tab for B before the tab for A, then data will be generated for all tabels. If I swap the two, no data is generated for B. This puzzles me because there are no interdependencies between these two tables. Any ideas?
Feature request: How about an abort/cancel/rollback/halt button for the Data Generator? It seems very fussy and very easy to crash it - and it usually brings the rest of the app down with it - there are times when the data in the test run looks correct, but attempting to generate into the database causes a crash, not sure why. Maybe some kind of error-checking too, getting the fields in the Master field wrong can also crash the app.
Version 7 (don't know if these issues are addressed in version 8).
I have two parent tables, A and B. They do not depend on each other, but have the SAME dependencies on two other tables.
I have several child tables. Some of the children depend on A, and some on B, and some on both. For tables that depend on A, I can set A.id as the master for the A_id field, and there are no problems generating data (I generate A.id from a simple sequence(1,1)). Tables that depend on B.id cannot be generated by the data generator. I have no idea why. The constraints and relationships are the same. Any tips/detailed instructions?
Sometimes the ordering matters: If I have the tab for B before the tab for A, then data will be generated for all tabels. If I swap the two, no data is generated for B. This puzzles me because there are no interdependencies between these two tables. Any ideas?
Feature request: How about an abort/cancel/rollback/halt button for the Data Generator? It seems very fussy and very easy to crash it - and it usually brings the rest of the app down with it - there are times when the data in the test run looks correct, but attempting to generate into the database causes a crash, not sure why. Maybe some kind of error-checking too, getting the fields in the Master field wrong can also crash the app.
Version 7 (don't know if these issues are addressed in version 8).
