On 19 July 2015 at 09:11, Rafal Pietrak <rafal@ztk-rp.eu> wrote:
I'm not particularly fond of using functions to accessing RDBMS instead of tables.
And I'm not particularly fond of "workarounds".
Use a combination of factors (a sequence ID and the key) for your authorization. So in the extremely unlikely event that the random key isn't unique, it doesn't matter. That's not a workaround, it's good design.
You're asking for a feature that is completely unnecessary and is easily resolved. UPSERT is designed for a situation which is neither.