Without an example, I can only guess at the requirement, but the best way to avoid different signatures is to use a flexible record type or sys.anydata. Or json. There is always a way to avoid duplicate code, and in many cases, dynamic execution can also be avoided or at least sufficiently secured.

do you have an example for the second?

and dynamic execution is no workaround?

can you describe your use case?

fun fact: oracleapex.com still runs on 19.23 ;-)

I know, and I'm fine with that for now. However, I had prepared myself for some new features, but those projects are now on hold. At least it would be nice to know if and when we can expect them. 19c won't be around forever, and I doubt all the features will be backported in the near future.

I wish I could say the same. Unfortunately, the currently available options - cloud, free, and beta - are not an option for me, at least not at the moment.

Most of us are waiting for a stable on-premises server release, but according to document ID 742060.1, these are still TBA.

I understand if the release is being held back due to bugs, but a little more open communication from Oracle would be really helpful.