
How to Use BULK COLLECT with LIMIT in PL/SQL
Read and change any number of rows in batches with BULK COLLECT LIMIT: 253 MB of PGA becomes 7 MB, with the right batch size and the exit condition that loses rows.

Read and change any number of rows in batches with BULK COLLECT LIMIT: 253 MB of PGA becomes 7 MB, with the right batch size and the exit condition that loses rows.

Create an email template with placeholders and an optional note, send it with APEX_MAIL.SEND on order approval, and test the mail and the page.

Build a weekly emailed report with a recipients table, a package, a weekly automation schedule, and tests for attachments and empty lists.

Build a forgot password flow with a hashed one-time token, an emailed link, a reset page, and tests for used and expired links.

Schedule a REST synchronization, understand Merge versus Replace, remove deleted rows, refresh only changed rows, and read the sync log.

Set up ORDS, an OAuth client, a web credential, and a REST Enabled SQL Service, then build an interactive report on remote tables.

Read the scheduler views in a report, add Run Now, Enable and Disable links with a safe procedure and an action log, and limit the page to administrators.

Run a page with debug on, find the slowest step in View Debug and APEX_DEBUG_MESSAGES, add an index and compare the times.

Create a build option, apply it to a report region and a menu entry, test Exclude and Include, and switch it with APEX_UTIL.

Send browser errors to the database with a static file, an Ajax callback process and an administrator report that groups the errors by page.

Use the activity log to see which pages are used most, which are slow and who opens them, with a period filter and an administrator-only page.

Build a secure share link in Oracle APEX with a random token, an expiry time, a view counter and a revoke button, and test it as a visitor without a sign-in.

Oracle covers a lot of ground. A developer who works with it may write SQL and PL/SQL in the database in the morning, build an Oracle APEX page after lunch, look after an Oracle Forms application that has run the…

Build a public Oracle APEX page that needs no login, limit what it shows to safe data and prove that the other pages still ask for a sign-in.

Allow access to an application only during business hours with an authorization scheme, an hours table, a test clock and admin exceptions.

Allow only one active session per user by ending older sessions at sign-in, with a limit table, a log and a test with two browsers.

Let visitors request an account, approve or reject the request on an admin page, and refuse sign-ins until the account is approved.

Use the built-in first-use switch for APEX accounts, or build a flag, a change page and a redirect for your own user table.