Instead, we use Oracle Application Contexts to hold session-specific information. Therefore, it is imperative that all my database code assumes nothing about the state of package variables, for example. Now, remember that APEX is a stateless environment as far as database sessions are concerned: when a page is requested, it might be generated by any session running on the database it might re-use a session that had just finished rendering a page for someone else entirely.
My APEX pages can query any table, no WHERE clauses needed (except for user-entered filters), and I can be confident they won’t be able to inadvertently see rows they’re not supposed to see if I forget to add the right predicate on every page that queries each table. This has made a potentially very complex application very simple. My current project uses Oracle RLS (Row Level Security) to ensure each user can only see the data they’re allowed to see. Home APEX APEX and Application Contexts APEX and Application Contexts
0 kommentar(er)
