Tidy badly encoded DB TABLE french chars

-
These few SQL lines came in handy when wanting a quick-fix for a poorly imported table

UPDATE [rpt].[dbo].[vapProducts] SET Region = replace(Region,'Á©','é')

UPDATE [rpt].[dbo].[vapProducts] SET Region = replace(Region,'Á´','ô')

UPDATE [rpt].[dbo].[vapProducts] SET Region = replace(Region,'ÁŽ','Î')



http://stackoverflow.com/questions/5127744/how-to-convert-these-strange-characters-%C3%83-%C3%83-%C3%83%C2%AC-%C3%83%C2%B9-%C3%83


Comments

Post a Comment

Popular posts from this blog

How do you fix a roll of aluminium foil once it's started spiralling?

-
I had this problem. Seen a post on Reddit .  Old one. " This thread is archived New comments cannot be posted and votes cannot be cast" That is a shame.  As I now have a better answer than any of the posts. Get a pair of tweezers and scrape down from the part of the foil roll that is "stuck".   Don't matter if it digs down into the layer beneath.  Try to maintain even digging across the roll. Worked a treat!
Read more

Why does Premiere Pro "Sequence from clip" on MP4 and then "Match Sequence" result in a massive AVI file?

-
Image
Good Question! You would imagine that just "trimming" an MP4 file with same setting would be quick and painless, but when I tried it the resultant file was massive - like 10x the size of the original file. https://community.adobe.com/t5/premiere-pro-discussions/match-sequence-settings-mp4-to-mpeg-is-this-normal/td-p/11042944 Turns out this is because the .mp4 compression means there aren't really full frames in the file just deltas. So when you select "Match Sequence Settings", it has to give you AVI format anyway. So this is what you HAVE to do.   Go ahead and create your HUGE AVI file.  Then use an app or an online service to compress it back down... I had a good result using  https://cloudconvert.com/avi-to-mp4 It shrunk the 76Mb AVI to less than half a Mb.  
Read more

Distributed Backlink Service

-
Wouldn't it be great to work together and create a "distributed search engine" with the index spread across thousands of peer nodes - a Google beating thing of beauty and love and money. Sadly the latency, speed, algorithmic and storage requirements make this a non-starter .  Try the state-of-the-art example like  yacy  and you'll see what I mean. It's just occurred to me - something that might be as least as lucrative ( 1 , 2 , 3 ) is a "link database" - and several factors easier to code and manage..... ....Who fancies giving it a go?
Read more