I created a little database in the new version and tested this. I don't think I have any Insert triggers, so I have no idea how it used to work with an "unload".
Unload All. The stored procedure and then the trigger are at the very end of the file after data is loaded. So that's perfect, just as it should be. But if I unloaded the structure into one file, and the data into another file (which is what I prefer to do): Unload Structure. I see the stored procedure and trigger are in this file. I run it first and my empty table is created with SP and trigger Unload Data. When I run this file, for each row in the table it evaluates the Insert trigger. Depending on what your insert trigger is doing, this could be an issue. Plus if you were reloading thousands of rows of data, it would evaluate the trigger for each of those rows. So the lesson is, if you do two separate unloads, you should remark out any Insert triggers and apply it after you've brought in the data. Karen -----Original Message----- From: 'Karen Tellef' via RBASE-L <[email protected]> To: [email protected] <[email protected]> Sent: Mon, Mar 8, 2021 9:28 am Subject: Re: [RBASE-L] - Tip of the Day: Enhanced UNLOAD Output for Stored Procedures - a question I think I'll put that on my list of "things to try" and see what happenswith an Insert trigger. I don't use triggers much, just a couple updatesand deletes which wouldn't be affected by an Unload Karen -----Original Message----- From: A. Razzak Memon <[email protected]> To: [email protected] Sent: Mon, Mar 8, 2021 9:19 am Subject: Re: [RBASE-L] - Tip of the Day: Enhanced UNLOAD Output for Stored Procedures - a question Using the latest update of R:BASE X.5, I suggest to try everything first, and then make any comments, if necessary. Very Best R:egards, Razzak At 10:04 AM 3/8/2021, 'Karen Tellef' via RBASE-L wrote: >I'm trying to figure out how this would work. If you had an INSERT >Trigger on a table and did an UNLOAD ALL, when you bring the file in >would it execute the insert trigger for every that's >reloaded? That's something to be concerned about if it's true. I >always separate an Unload Structure and Data, never do an "all" if I >can help it, so it would be possible to modify the structure file >and delete the trigger command. I'm thinking that trigger commands >should come after the data is loaded into a table? > >Karen > >-----Original Message----- >From: A. Razzak Memon <[email protected]> >To: [email protected] >Sent: Mon, Mar 8, 2021 8:37 am >Subject: [RBASE-L] - Tip of the Day: Enhanced UNLOAD Output for >Stored Procedures > >Monday, March 08, 2021 > >Tip of the Day: Enhanced UNLOAD Output for Stored Procedures >Product.......: R:BASE X.5 and R:BASE X.5 Enterprise (Version 10.5) >Build.........: 10.5.3.20304 or higher >Sections......: Commands >Keywords......: UNLOAD, STRUCTURE, DATA, Stored Procedure > >Did you know that the UNLOAD STRUCTURE and UNLOAD DATA commands >were enhanced with the generated output, where stored procedure >data is now placed in the structure output? > >The UNLOAD STRUCTURE output now includes stored procedure data, >before triggers, allowing the file output from subsequent UNLOAD >STRUCTURE and UNLOAD DATA processes to be utilized for database >rebuilds. With this change, stored procedure data is not unloaded >as part of the data unload. > >Also, when performing an UNLOAD ALL, you will now see the procedure >data in its new location (right before triggers) rather than in the >middle of the data for all the other tables. > >If your output is going to the SCREEN, rather than a file, and you >do an UNLOAD which requires LOB output, a SCREEN.LOB file will be >created in the current directory. > >The end result allows database with stored procedures to be easily >rebuild from the separated UNLOAD STRUCTURE and UNLOAD DATA output, >which is helpful in database maintenance! > >Very Best R:egards, > >Razzak. > >https://www.rbase.com >http://www.facebook.com/rbase/ > > >-- >For group guidelines, visit >http://www.rbase.com/support/usersgroup_guidelines.php >--- >You received this message because you are subscribed to the Google >Groups "RBASE-L" group. >To unsubscribe from this group and stop receiving emails from it, >send an email to [email protected]. >To view this discussion on the web visit >https://groups.google.com/d/msgid/rbase-l/0MAxNa-1lQvzz3kEW-00A27R%40mrelay.perfora.net. > >-- >For group guidelines, visit >http://www.rbase.com/support/usersgroup_guidelines.php >--- >You received this message because you are subscribed to the Google >Groups "RBASE-L" group. >To unsubscribe from this group and stop receiving emails from it, >send an email to [email protected]. >To view this discussion on the web visit >https://groups.google.com/d/msgid/rbase-l/1405242385.483513.1615215840617%40mail.yahoo.com. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/1MXYdX-1lFhzm0cBz-00Z3Ge%40mrelay.perfora.net. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/522885605.495367.1615217307706%40mail.yahoo.com. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/1735179197.645204.1615241814097%40mail.yahoo.com.
