Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Another handy difference (in English where accents are uncommon) is that an InvariantCulture comparison compares the entire strings by case-insensitive first, and then if necessary (and requested) distinguishes by case after first comparing only on the distinct letters. (You can also do a case-insensitive comparison, of course, which won't distinguish by case.) <strong>Corrected:</strong> Accented letters are considered to be another flavor of the same letters and the string is compared first ignoring accents and then accounting for them if the general letters all match (much as with differing case except not ultimately ignored in a case-insensitive compare). This groups accented versions of the otherwise same word near each other instead of completely separate at the first accent difference. This is the sort order you would typically find in a dictionary, with capitalized words appearing right next to their lowercase equivalents, and accented letters being near the corresponding unaccented letter.</p> <p>An ordinal comparison compares strictly on the numeric character values, stopping at the first difference. This sorts capitalized letters completely separate from the lowercase letters (and accented letters presumably separate from those), so capitalized words would sort nowhere near their lowercase equivalents.</p> <p>InvariantCulture also considers capitals to be greater than lower case, whereas Ordinal considers capitals to be less than lowercase (a holdover of ASCII from the old days before computers had lowercase letters, the uppercase letters were allocated first and thus had lower values than the lowercase letters added later).</p> <p>For example, by Ordinal: <code>"0" &lt; "9" &lt; "A" &lt; "Ab" &lt; "Z" &lt; "a" &lt; "aB" &lt; "ab" &lt; "z" &lt; "Á" &lt; "Áb" &lt; "á" &lt; "áb"</code></p> <p>And by InvariantCulture: <code>"0" &lt; "9" &lt; "a" &lt; "A" &lt; "á" &lt; "Á" &lt; "ab" &lt; "aB" &lt; "Ab" &lt; "áb" &lt; "Áb" &lt; "z" &lt; "Z"</code></p>
    singulars
    1. This table or related slice is empty.
    1. PODifference between InvariantCulture and Ordinal string comparison
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRob Parker
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. COI took another look at this and noticed an inconsistency between the InvariantCulture example and my explanation on the handling of accented characters. The example appears to be correct, so I've corrected the explanation to be consistent. The InvariantCulture comparison does not stop at the first differing accent and appears to only consider an accent difference on the same letter if the rest of the strings match besides accents and case. An accent difference is then considered before an earlier case difference, so "Aaba" < "aába".
      singulars
      1. PO
      1. USRob Parker
 

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