Re:RFC6238 TOTP implementation in pure PostgreSQL
by smallnamespace on Thursday February 25, 2021 @03:11AM
(#26260780)
Right, except if my backend is in JS, there's a cognitive cost to adding another language to the stack.
I could use plv8, but there's a more subtle preference here for JS to wrap SQL, rather than the reverse (plus tooling is less convenient, e.g. if you're writing Typescript).
My rule of thumb is: SQL great, PL not so much.
Re:RFC6238 TOTP implementation in pure PostgreSQL
by e12e on Thursday February 25, 2021 @06:30AM
(#26261842)
> except if my backend is in JS, there's a cognitive cost to adding another language to the stack.
Agreed.
However, I don't see why not use one of the other mature "real" extension languages other than pl/pgSQL.
As for typescript, maybe there's (distant) hope:
Not really? Postgres (as well as other rdbms) support many other languages - I don't see many good reasons to insist on pl/pgSQL for uses like these?
Both python, perl and TCL are part of the standard distribution in addition to pl/pgSQL.
https://www.postgresql.org/docs/13/xplang.html
https://www.postgresql.org/docs/13/external-pl.html