Oracle APEX Developer • AI Builder • Practical guides on APEX, SQL & Automation.
Hi, I'm Arfaat Shaikh, an Oracle APEX Developer with a passion for building scalable, user-friendly enterprise applications. I enjoy solving real-world problems using Oracle APEX, PL/SQL, SQL, REST APIs, and AI-powered solutions. Through this blog, I document practical Oracle APEX tutorials, production-ready solutions, troubleshooting guides, and best practices from my development journey. My goal is to make complex concepts simple and create resources that help developers learn faster and build with confidence. Whether you're just getting started with Oracle APEX or looking for advanced techniques, I hope you'll find something useful here. Happy coding!
Markdown supported · ⌘↵ to post
Steven Mock
This is a useful breakdown, especially the part most people skip: every method has to end on the same user row, or you slowly end up with one person holding two accounts. Mapping by Google's sub first, then by email, is the right order — I've seen the duplicate-account mess that comes from matching on email alone. The security checklist is the other piece I'd underline. More ways in really does mean more doors to lock, and checking the same rules for every method is what keeps it honest. Do you have a plan for when a member changes their Google email — does the sub still carry them through cleanly?