@phsalvisberg@GebalJacek I think the other angle to this is, will your company put in the time and money to keep checking the security of your closed source code? This is not a one-time-and-done situation. I suspect many of these flaws would have remained in the code if it were not open source.
AI agents will break your dev schema. So give each one its own database.
New post in my APEX Developer Reinvented series: how I use Oracle SNAPSHOT COPY to spin up a PDB per ticket in seconds, and drop it after the merge.
https://t.co/fyOEsVFs33
#JoelKallmanDay#orclapex
My contribution to #JoelKallmanDay A quick read about the Oracle ACE program.
If you want to be an ACE, please feel free to reach out to me.
https://t.co/cdyqWCU4sS
We’re incredibly grateful to the Oracle developer community for creating Joel Kallman Day, honoring Joel’s legacy of service above self. 🧡
Join us today by sharing something that inspires you, a technical insight or a personal story, using the hashtag #JoelKallmanDay.
#orclAPEX
Using 2 subreports in a jrxml template for as_pdf doesn't result in the expected output.
But passing variables back to the master reports works at least 🤣#JoelKallmanDay
Oracle Deep Data Security is so good; a brilliantly designed relational database enhancement.
But there is a big catch: it currently requires a Cloud Identity Provider, also for #orclAPEX ...
#JoelKallmanDay#Oracle#SQL
https://t.co/D5JVrszIpU