Overview
United Codes develops software solutions designed to enhance productivity. The company operates in the software development sector.
Key people
In the news
- APEX Project Eye 26.2 adds human-readable column labels to your Watchtower sensors. Open a sensor from an older release, and the report reads like a database export: headers like AT03 or VAL that only made sense to the person who wrote the SQL query. APE 26.2 lets you replace those raw identifiers with custom labels defined per sensor, so Watchtower reports read like your data. Your labels travel with the sensor when you export to JSON, work as placeholders in escalation messages, and give AI-generated summaries the context to
- Week 4 of the dbLinter series with Philipp Hartenfeller takes a security turn: rule G-9501, the caller writes your SQL. Here's a function that looks harmless. It accepts a table name, builds a count query by concatenating that name directly into the string, and then runs it with EXECUTE IMMEDIATE. The catch is that the caller's input lands directly in the statement, so anyone can append a UNION and read salaries or any other table they like. The database sees valid SQL and returns results without complaint. The safe version routes
- Thinking about bringing AI into your Oracle APEX development? Our latest newsletter opens with United Codes AI Services, a path that runs from a first AI Readiness Assessment through to ongoing support, with a human in the loop at every step. Also in this edition: • dbLinter now lints APEX applications with the first APEXlang rules • APEX Office Print 26.1.2 lets you sign PDFs with your eID card, straight from the browser • APEX Office Edit 26.1 adds multi-page view and change comparison • Five free plug-ins updated for APEX 26.1 •
- Week 3 of the dbLinter series with Philipp Hartenfeller, and this one is marked Critical: rule G-3210, one SQL call per row. Picture a PL/SQL block that loops over a collection of employee IDs and runs an UPDATE once per iteration. It compiles and runs fine, then slows to a crawl as the data grows. Each pass through the loop hands one statement to the SQL engine and waits, so every row pays for a context switch between the PL/SQL and SQL engines. Those switches add up fast. The upgrade is FORALL. Swapping the loop for a single
- 𝗢𝘂𝗿 𝗹𝗮𝘁𝗲𝘀𝘁 𝗔𝗻𝗰𝗵𝗿 𝗛𝗶𝗴𝗵𝗹𝗶𝗴𝗵𝘁𝘀 𝗶𝘀 𝗼𝘂𝘁! 🚀 A lot is happening across the Anchr group. Our software companies are growing, launching new solutions, taking on ambitious projects and creating impact for their customers and markets. In this September edition, we’ve brought together a selection of stories from across the group. Curious to see what’s moving across Anchr? 👉 Read the latest edition of Anchr Highlights and discover the stories behind our companies Bridg Contractify Legile Praclox B.V. Qobee
- Week 2 of our dbLinter series with Philipp Hartenfeller, and this one hides in plain sight: rule G-1240: index your foreign key columns. Here's the setup. A child table references a parent through a foreign key, and the parent_id column has no index. Deleting a single parent row still succeeds, but Oracle has to full-scan the child table to check for matching rows and takes a table-level lock while doing so. Concurrent writers sit and wait. The fix is a one-liner: create an index on the child's foreign key column. dbLinter goes a
- Kicking off a new weekly series with Philipp Hartenfeller: each week, one Oracle SQL or PL/SQL rule and the sneaky bug it prevents. First up is rule G-3185. Picture a query asking for your five highest-paid employees. It runs cleanly and returns five rows, handing you the wrong people without any warning. The cause is timing. ROWNUM gets assigned before ORDER BY sorts anything, so the database keeps the first five rows it happens to find and only sorts those. Switching to RANK() with FETCH FIRST resolves it, since FETCH FIRST
- Feeling so proud today! Our very own Vito Van Hecke just became an Oracle ACE Associate. ♠️ If you've ever seen Vito present, you know the spark he brings. He has a real love for sharing knowledge and a talent for making tricky APEX topics feel easy, and the whole community is better for it. This recognition means a lot, and nobody deserves it more. Congratulations, Vito. This milestone is thoroughly earned, and we can't wait to see where you take it next. #OracleAPEX #OracleACE #APEX #LowCode #orclapex #OracleACEAssociate
Related profiles
Something wrong or missing? Send an update. Fixed within 24 hours.