Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The first thing to remember, is that there is no such thing as a "special character" or an "illegal character". There are characters that are special in certain circumstances, there are non-characters, but there are no generally "special characters" or "illegal characters".</p> <p>What you have here is either:</p> <ol> <li>Perfectly normal characters for which your font doesn't have a glyph.</li> <li>Perfectly normal characters that aren't printable (e.g. control characters).</li> <li>An artefact of how the debugger works.</li> </ol> <p>The first thing is to find out what that character is. Find the integer value of the character, and then look it up.</p> <p>An important one to look out for is U+FFFD (�) as it is sometimes used when a decoder has recieved a bunch of bytes that make no sense in the context of the encoding it is trying to use (e.g. 0x80 followed by 0x20 makes no sense in UTF-8, and one possible response is to use U+FFFD as a "something strange here" marker, other possible responses are throwing an error, and also silently ignoring the error or trying to guess at intent though those last two bring security issues).</p> <p>Once you've this figured out, you can begin to reason about why it's getting in there if it isn't expected. Could it be an ecoding issue (charset written in is not the charset read in)? Could it be actually intended to be there? Could it be something else? You can't begin to answer that until you have more information on the bug.</p> <p>Finally, there's the matter of what to do about it. This will hopefully be obvious from the answers you've found in your research above. Possibly the answer will be "nothing it's fine", possibly something simple or something hard. Can't say yet.</p> <p><strong>Do not just filter with a regular expression</strong>. Maybe that will turn out to be the correct solution, but you don't know yet, so maybe you're making a deeper bug harder to find than it is now, or damaging perfectly good data.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to prevent illegal characters to appear in my XML when retrieving it from SQL Server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJon Hanna
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to prevent illegal characters to appear in my XML when retrieving it from SQL Server
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWell the XML in the database reads fine as "123-45-6789" but when I deserialize the XML back into an object on the client it reads "123[]45[]6789", is this all back to encoding?
      singulars
      1. PO
      1. USmint
    2. COPossibly. What is the value of (int)"123[]45[]6789"[3] here? That'll tell us a lot. For that matter, are you sure that the fourth character in the first string is - and not ‐,‑,–,‒ or — (indeed, ‒ would be better typography than - though not as useful in machine-readable contexts). That'll tell us something too.
      singulars
      1. PO
      1. USJon Hanna
    3. COWell when I ran this in the debuuger ?Char.GetNumericValue("12‑34‑5678", 2) it returned -1.0
      singulars
      1. PO
      1. USmint
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload