Overview
This tool can be used to quickly generate multiple rows for each of the application transactional tables to easily support database load testing.
Key Features & Functionality
If you have ideas for more generators, please leave a comment!
My initial test failed. It only worked after I checked the json Master and put {} in the Delete Settings column. Is there an instruction on how to use these fields? Thanks.
Hi Michael, I am on the latest version (1.2.1) and the issue above is still happening for me. Changing the deleteSettings value in the DG_TABLE table with the text "null" rather than null value is solving the issue for me.
With that change you won’t have the problem going forward. I have submitted a new version to app market that will make it so you don’t have to apply this change manually.
Thanks Michael. I deleted the table, configure it again and it is now working with the updated code.
Is this only happening on new install? I will relay this information to other teams but want to make sure if they will also be affected if upgrading to v1.0.8
I should have been more specific, the deleteSettings will fix it for new tables that are added. For any existing ones you should set them manually to null of the delete setting is none. Otherwise use the trash can link to confirm the delete settings.
Hi Michael, adding deleteSettings: "null" did not fix it. I also tried null without quotes and {}.
I'll just check the Master and set Delete Settings column to {}for now while waiting for the next version.
Thanks