APEX Instant Tips episode #200 is today at 12:05 Eastern time. Mike Hichwa is joining us. I hear there are things to talk about:
https://t.co/bpvJwHmoY5
Today on Instant Tips: Weighted Page Performance reporting...in Dev, in UAT, and, oh yeah, in Prod. with @c2anton and co-host @marwachouch. Join us at 12:05 pm EST!
https://t.co/NBg0r4IXdh
#APEXInstantTips#orclapex
@OliverLemm@orclapexworld How about a function that returns the query and adds
where 1=2
If there aren’t any query criteria. (Unless I’m missing the point.)
@plamen_9@haydenhhudson Very good but with subtle mistakes. For example, we described how to call different template components from one column but in the second summary it describes it the other way around.
Overall, it would save a lot of typing and just require a little review to straighten out.
I don't know if I mentioned these here before, but I updated both of these recently #orclapex:
This one should be interesting to a lot of people
https://t.co/nUKq9zT7G6
This one is pretty specific and a little boring
https://t.co/fnnqm4aHxA
Tomorrow's APEX Instant Tip is a best practice hiding in the shadows. It should change the way most of us develop in APEX. I haven't learned something so fundamental about APEX in a long time. #orclapex
https://t.co/6xnrZTQK0L
@nlitchfield@richsoule@fdernoncourt@oracleace Hmmm...wow. I'm going to have to think about this. Maybe I drank too much CoolAide while I was at Oracle in the 2000's when Larry just wanted "all of your data" in the Oracle database.
@mortenbraten@richsoule The highlighted sentences don’t attempt to answer the question of when the builder should be allowed in production. There is a huge range of how we use a database. I’m interested in discussing the vulnerabilities of having the builder in production. I’ll work on that :)
@krisrice@mortenbraten I should stay off Twitter. Now I need a blog post…too long for a tweet. Perhaps I should have started here: focusing on an individual definition of “develop” will miss the broader themes of “appropriately protect the data” and “appropriately protect the computing resources.”
@mortenbraten Where do you draw the line? What is the most you will allow without calling it developing? It’s not so easy to answer. But if you can’t answer that, then you can’t even say if you allow development in production. For me, it’s now “if” but “how much.”
@mortenbraten If you have a single IR with 15 columns that might have filters, that’s 2^15 (32,768) possible dynamically generated queries. 32K different explain plans. No way people test them all. If you haven’t tested it, then you are developing in prod.