Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options answers only user 30859
4
votes
difference with having some Unicode characters vs not having any is that without any Unicode characters it can convert the string to an 8-bit encoding (i.e. single byte for use with VARCHAR), but … is 3999 characters that can convert cleanly into an 8-bit encoding (i.e. VARCHAR) plus the U+3000 character that will likely remain as 2 bytes. So maybe this comes across, through that software, as …
answered Jul 21 '17 by Solomon Rutzky
10
votes
While I am not sure of the exact reason for those specific characters, t The issue has to do with the older collations (please see UPDATE section at the end). And it is not just empty string that they …
answered May 25 '15 by Solomon Rutzky
2
votes
Are strings in table columns represented as bit patterns or Unicode? Computers only deal with 1's and 0's (i.e. binary); datatypes indicate how to interpret that info. Would the queries perfo …
answered May 24 '15 by Solomon Rutzky
5
votes
complicated nature of text encoding, especially non-Unicode encodings. Everything is just bytes. What we see on the screen is just an interpretation of those bytes. One encoding may certainly display … a different "character" than another encoding for the same byte, or byte-sequence (depending on the encoding), but technically, bytes are bytes and all bytes are valid. In the case of Â, you can't …
answered Nov 8 '17 by Solomon Rutzky
1
vote
According to the MSDN page for PDO::setAttribute, PDO::SQLSRV_ENCODING_UTF8 is the default value, so setting it explicitly probably wouldn't change the behavior. Try the other option, PDO::SQLSRV_ENC …
answered Jun 5 '16 by Solomon Rutzky
26
votes
The trick here is to realize that these characters that you see in the question with the "accents" aren't really the characters (i.e. "These aren't the droidscharacters you are looking for" ;-) ). The …
answered Dec 4 '14 by Solomon Rutzky
2
votes
Depending on what RDBMS you are using: You can try altering the Latin1-encoded column to use an encoding of UTF-8, if the RDBMS supports such an operation. If you are using MySQL, you should look … at this related Question on S.O.: Converting mysql tables from latin1 to utf8 You can try: Adding a new column with an encoding of UTF-8 UPDATE new_column = Latin1_column (I am assuming that the …
answered Jan 28 '16 by Solomon Rutzky
7
votes
). According to that MSDN page for Character Encoding in the .NET Framework: Best-fit mapping is the default behavior for an Encoding object that encodes Unicode data into code page data... But what …
answered Nov 29 '15 by Solomon Rutzky
5
votes
additional steps (and CPU cycles) it takes to do those encoding translations. So far this is just a theory as I have not tested it. …
answered Nov 1 '18 by Solomon Rutzky
1
vote
I need to insert this character '●' into a VARCHAR column ... with collation set as SQL_Latin1_General_CP1_CI_AS ... The reason I am doing this exercise is that our app was inserting this character …
answered Nov 20 '18 by Solomon Rutzky
2
votes
The PostgreSQL documentation leaves a lot to be desired (just sayin' 😼 ). To start with, there is only one encoding for a particular database, so C and C.UTF-8 in your UTF-8 database are both using … the UTF-8 encoding. For libc collations: typically collation names, by convention, are truly two-part names of the following structure: {locale_name}.{encoding_name} A "locale" (i.e. "culture") is …
answered Jun 19 by Solomon Rutzky
4
votes
tables and columns and not specifying a Collation via the COLLATE keyword. Step 1: File Encoding BCP / BULK INSERT (or most any other code reading a file) will not know what encoding a file is using … (I prefer chcp as it also allows for changing the code page if you pass in a value). If your default code page is 850 and yet the file was saved with an encoding of Windows-1252 Latin1 (ANSI), then …
answered Dec 30 '16 by Solomon Rutzky
0
votes
If you can manually change the encoding (to one that includes the Byte Order Mark) and have it work such that no characters are lost, then the file itself is fine. It seems that the tablediff … utility does not allow for specifying the encoding type of the output file, so you are left with two options: Configure SSIS to specify that script as being UTF-8 rather than relying upon the default …
answered Jun 9 '16 by Solomon Rutzky
2
votes
I was running into problems when people would query for an emoji in the database and my React app would throw an error What was the exact error message? What were the character set and collation …
answered Sep 26 by Solomon Rutzky
6
votes
Arabic (as well as Hebrew and Syriac) are right-to-left languages. Hence they display in the opposite direction that the bytes are physical stored in. Having the proper display is controlled through n …
answered Dec 29 '18 by Solomon Rutzky

15 30 50 per page