3 ms·
This strikes me as data validation, which should reside in the application layer - I don't see how pg-emoji helps in any way. Further... if the receiver can va
by Ancapistani 6y ago
This strikes me as data validation, which should reside in the application layer - I don't see how pg-emoji helps in any way.
Further... if the receiver can validate the encoded string itself, they implicitly already have the string. Why require the user to copy/paste at all? If you meant "Ensure that the user hasn't copied quotation marks as well", then we're back to it being application logic.
If I'm understanding correctly that the primary benefit is that there is a checksum, then there are already many solutions for this in common use - base58checksum, as used to ensure the validity of Bitcoin addresses, comes immediately to mind. I wrote an implementation of that quite a while ago: https://github.com/lyndsysimon/cryptocoin/blob/primary/cryptocoin/base58.py https://github.com/lyndsysimon/cryptocoin/blob/primary/crypt...
Please don't misunderstand, I'm in no way intending to be argumentative. I don't understand the practical use of this project, which leads me to believe that there is a problem being solved that I lack the context to identify.
- JoelJacobson 6y agoIn my case, PostgreSQL is the application layer, the application is written in database functions, and I’m using PostgREST to expose it to my front-end.
- Ancapistani 6y agoAh, that makes more sense then.