tag:blogger.com,1999:blog-21169145.post7739899025157181657..comments2023-04-29T14:41:38.880+02:00Comments on Jornica: APEX_GLOBAL_ARRAYSJornicahttp://www.blogger.com/profile/15492511382521784329noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-21169145.post-70334919977981568672010-02-09T21:38:29.623+01:002010-02-09T21:38:29.623+01:00Edward,
Yes, it should work. The first argument ...Edward, <br /><br />Yes, it should work. The first argument of apex_item refers to the number of the global array.<br /><br />With kind regards,<br /><br />JornicaJornicahttps://www.blogger.com/profile/15492511382521784329noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-30721158732195437652010-02-09T21:38:28.206+01:002010-02-09T21:38:28.206+01:00Edward,
Yes, it should work. The first argument ...Edward, <br /><br />Yes, it should work. The first argument of apex_item refers to the number of the global array.<br /><br />With kind regards,<br /><br />JornicaJornicahttps://www.blogger.com/profile/15492511382521784329noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-90723009780485040272010-02-08T02:51:15.173+01:002010-02-08T02:51:15.173+01:00Jornica,
should it work for manual tabular form b...Jornica,<br /><br />should it work for manual tabular form based on apex_item calls?<br /><br />Thanks.<br /><br />EdwardUnknownhttps://www.blogger.com/profile/05335334357433847509noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-46008990926110194642008-03-04T22:47:00.000+01:002008-03-04T22:47:00.000+01:00Jorrit,Thanks for the reply. Unfortunately, I'm n...Jorrit,<BR/><BR/>Thanks for the reply. Unfortunately, I'm not seeing the array show up after Submit. In fact, I'm not seeing it at all anymore. But I think just re-reading your post helped me realize that some arrays are sparse, which I wasn't taking into account. Thanks for that tip!<BR/><BR/>Maybe I need to disable my processes that run after Submit?Stewhttps://www.blogger.com/profile/05177922393895344852noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-11093236375085979382008-03-02T22:44:00.000+01:002008-03-02T22:44:00.000+01:00Stew, That the way APEX works:When you press the s...Stew, <BR/><BR/>That the way APEX works:<BR/>When you press the submit button a request is sent to the APEX engine, which generates a new page. Any debug information will be on this new page. <BR/><BR/>With kind regards, <BR/><BR/>JorritJornicahttps://www.blogger.com/profile/15492511382521784329noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-10215527046924269552008-02-29T19:28:00.000+01:002008-02-29T19:28:00.000+01:00Jornica,Yeah I was just being dumb. I mistakenly ...Jornica,<BR/><BR/>Yeah I was just being dumb. I mistakenly <B>assumed</B> that you were talking about a <B>standard</B> Apex package, not one you'd (kindly) provided.<BR/><BR/>Before I read your patient response, I noticed there was a download link, so I installed it in the right schema and created an On Submit (before validation and calculation process). <BR/><BR/>When I click the Developer Debug link, it refreshes the page and shows all the debug details. I'm surprised that it shows the global arrays here, since I set its condition for REQUEST IN SUBMIT.<BR/><BR/>And if I change a data value and click Submit, it doesn't print the arrays before it starts processing.<BR/><BR/>Did I totally misunderstand the point here? I thought it would show you the latest changes before your On Submit post-processing runs. Not so much???<BR/><BR/>Thanks,<BR/><BR/>Stew<BR/><BR/>p.s. Hey, I may be slow, but at least I'm willing to admit it! :-/Stewhttps://www.blogger.com/profile/05177922393895344852noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-9580721814345574512008-02-27T21:29:00.000+01:002008-02-27T21:29:00.000+01:00Stew,You can install APEX_GLOBAL_ARRAYS in the par...Stew,<BR/><BR/>You can install APEX_GLOBAL_ARRAYS in the parsing schema or in a separate schema. <BR/><BR/>Did you install the package in the parsing schema? You can find the parsing schema of your application on application definition page. <BR/><BR/>When you choose for a separate schema you have to grant execute right to the parsing schema and create a (public) synonym for APEX_GLOBAL_ARRAYS (or prefix the call with schema owner but prefixing is not considered good practice).<BR/><BR/>I don't think you can blame your DBA, but you can try anyway ;-). Your comment also reminds me to add a note about the installation.<BR/><BR/>With kind regards,<BR/><BR/>JornicaJornicahttps://www.blogger.com/profile/15492511382521784329noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-27153562065019065202008-02-27T19:37:00.000+01:002008-02-27T19:37:00.000+01:00Man, I'm feeling stupid today, but I can't seem to...Man, I'm feeling <B>stupid</B> today, but I can't seem to get this to work.<BR/><BR/>I put the following into a new page process:<BR/><BR/>BEGIN<BR/> apex_global_arrays.print();<BR/>END;<BR/><BR/>and Apex replies with the error:<BR/><BR/>ORA-06550: line 3, column 5: PLS-00201: identifier 'APEX_GLOBAL_ARRAYS.PRINT' must be declared<BR/><BR/>It's a sad statement of my level of Apex sophistication that I'm <B>hoping</B> this is an Apex installation error on the DBA's part, not that I can't use something so basic properly! :-/<BR/><BR/>Thanks for any help you choose to give (after you finish laughing).<BR/><BR/>- StewStewhttps://www.blogger.com/profile/05177922393895344852noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-40255233881652363572008-02-14T22:43:00.000+01:002008-02-14T22:43:00.000+01:00The advantage of using the declarative condition i...The advantage of using the declarative condition is that it can be handled "hard wired" by the APEX engine.<BR/><BR/>If you don't use this condition, the APEX engine always has to create a dynamic PL/SQL call for your procedure, the procedure is called, the if for debug is checked...<BR/><BR/>Much more processing than the declarative check. PL/SQL in APEX cost always more and the declarative check.<BR/><BR/>Greetings<BR/>PatrickPatrick Wolfhttps://www.blogger.com/profile/16652802762749621200noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-69397857881380496192008-02-14T22:30:00.000+01:002008-02-14T22:30:00.000+01:00Patrick,Thanks for the idea of calling it from an ...Patrick,<BR/><BR/>Thanks for the idea of calling it from an application process. However the condition is not necessary. The procedure only prints when run in debug mode, otherwise only one IF statement is executed.<BR/><BR/>With kind regards,<BR/><BR/>JornicaJornicahttps://www.blogger.com/profile/15492511382521784329noreply@blogger.comtag:blogger.com,1999:blog-21169145.post-57304603215488057432008-02-14T00:15:00.000+01:002008-02-14T00:15:00.000+01:00Jornica,very interesting and useful tip!Putting th...Jornica,<BR/><BR/>very interesting and useful tip!<BR/><BR/>Putting that into an application level "On Submit" process with a condition "item IS NOT NULL" for DEBUG would easily enabled it globally for an application.<BR/><BR/>Great work!<BR/>PatrickPatrick Wolfhttps://www.blogger.com/profile/16652802762749621200noreply@blogger.com