Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Re: [OT] SQL "on duplicate key" custom actionby cavac (Parson) |
on Oct 21, 2019 at 15:12 UTC ( [id://11107767]=note: print w/replies, xml ) | Need Help?? |
If you have the choice, choose PostgreSQL. It might not matter in the beginning, but projects tend to grow in complexity and PostgreSQL is a much better fit when it comes to complex data handling tasks and keeping your data integrity intact. Also, if you like PerlMonks, you will most likely enjoy working with the PostgreSQL community.
perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'
In Section
Seekers of Perl Wisdom
|
|