Re:UTF-7: a ghost from the time before UTF-8
by dvtrn on Friday November 30, 2018 @03:44PM
(#18572466)
You're probably right that it's not a rare problem, but at the right scale it can be a business ending problem.
Re:UTF-7: a ghost from the time before UTF-8
by k__ on Friday November 30, 2018 @03:48PM
(#18572498)
True.
I'm just amazed that there seems to be a fair amount of back-end developers who don't know anything about this. Probably because SQL systems are used at more conservative companies with older customers?
Re:UTF-7: a ghost from the time before UTF-8
by dvtrn on Friday November 30, 2018 @03:55PM
(#18572538)
That's a good question. I think part of this can be attributed to the efforts taken by the database World to demystify database operations and abstract some of the processes to the point where infrastructure by click became easy enough for these problem to be completely forgotten about or overlooked by your modern developer doing business as DBA (swidt?).
Can insert? Can query? Nothing more to do here.
When I did a web project in university in 2014, the assistant professor warned me at the beginning that this will happen with MySQL and Emoji, because he had the problem the last semester.
And then in 2017, years after I learned that this was a huge problem, I got a freelance app project where they already had a back-end developer. The app crashed multiple times after release when I finally realized the back-end dev didn't know anything about this and simply clicked together the DB in phpmyadmin with all the default settings...