tag:blogger.com,1999:blog-7849367040589270673.post5059597811953089907..comments2024-03-21T22:50:39.997-07:00Comments on Obsessed with Oracle PL/SQL: Enhanced Code Accessibility Management in 12.2Steven Feuersteinhttp://www.blogger.com/profile/18405765731886460622noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-7849367040589270673.post-51880363927290383772017-02-28T08:21:08.354-08:002017-02-28T08:21:08.354-08:00Thanks for your Support.
Now I got solution for my...Thanks for your Support.<br />Now I got solution for my new logic to implement in my code.Surya1525https://www.blogger.com/profile/10301198304577286357noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-85045901501529479802017-02-28T04:20:58.575-08:002017-02-28T04:20:58.575-08:00Surya, I am not really sure what you are asking. Y...Surya, I am not really sure what you are asking. You show an example of a dynamic REFERENCE to a table, but other than that I do not know what you mean by "dynamic table". If you mean a table that is created at runtime via a call to execute immediate, then sure, right after you create the table dynamically, you can create your trigger the same way.Steven Feuersteinhttps://www.blogger.com/profile/18405765731886460622noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-26627626064905359282017-02-27T21:18:35.809-08:002017-02-27T21:18:35.809-08:00Hi Steven,
I would like to say thank you,because ...Hi Steven,<br /><br />I would like to say thank you,because your blogs are help full for me to implement logic for writing new code.<br /><br />I have one query ...........<br />Is it possible to create trigger on dynamic Table?<br /><br />Table is created dynamically like "Table_||seq.nextval".<br /> Surya1525https://www.blogger.com/profile/10301198304577286357noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-81541286290819656782017-02-17T06:10:25.425-08:002017-02-17T06:10:25.425-08:00Thanks so much for bringing your usual excellent s...Thanks so much for bringing your usual excellent scrutiny to bear on my writings, Iudith. I have made changes to the post and given you credit. Steven Feuersteinhttps://www.blogger.com/profile/18405765731886460622noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-70743005248006415402017-02-15T17:35:15.883-08:002017-02-15T17:35:15.883-08:00Hello Steven,
Just two short remarks:
1. As by t...Hello Steven,<br /><br />Just two short remarks:<br /><br />1. As by the documentation, specifying the 'unit kind' in the ACCESSIBLE BY clause was also available in 12cR1.<br /> Specifying TRIGGER was mandatory, so, when 'unit kind' was NOT specified, <br />it was implied as one of "the other namespace"<br /> ( FUNCTION, PACKAGE, PROCEDURE or TYPE ).<br /><br /> So, if we wanted to make a unit accessible from both a trigger and another unit having the same name,<br /> then we should have probably had to specify the two accessors separately,<br /> while in 12.2 it is sufficient to omit the unit kind entirely.<br /><br /><br />2. In the procedure this_for_pkgd_proc1_only, when you specify "ACCESSIBLE BY (PROCEDURE pkg1.myproc1)",<br /> the accessor is interpreted as PROCEDURE myproc1 from schema pkg1.<br /><br /> If you wanted to reference package pkg1, the syntax should have been <br /> "ACCESSIBLE BY (PACKAGE pkg1)" and, indeed, it is NOT possible to specify a specific procedure from that package, like in "ACCESSIBLE BY (PACKAGE myschema.pkg1.myproc1)".<br /> Using such a syntax produces compilation error.<br /><br />Best Regards,<br />Iudith<br />iudithhttps://www.blogger.com/profile/04905902445036068357noreply@blogger.com