Knowledge

Case sensitivity

Source 📝

78:: Users expect information retrieval systems to be able to have correct case sensitivity depending on the nature of an operation. Users looking for the word "dog" in an online journal probably do not wish to differentiate between "dog" or "Dog", as this is a writing distinction; the word should be matched whether it appears at the beginning of a sentence or not. On the other hand, users looking for information about a brand name, trademark, human name, or city name may be interested in performing a case-sensitive operation to filter out irrelevant results. For example, somebody searching for the name "Jade" would not want to find references to the mineral called "jade". On the English Knowledge for example a search for 20: 372:
are internally case-sensitive, and a readme.txt and a Readme.txt can coexist in the same directory. However, for practical purposes filenames behave as case-insensitive as far as users and most software are concerned. This can cause problems for developers or software coming from Unix-like
285:
A text search operation could be case-sensitive or case-insensitive, depending on the system, application, or context. The user can in many cases specify whether a search is sensitive to case, e.g. in most text editors, word processors, and Web browsers. A case-insensitive search is more
286:
comprehensive, finding "Language" (at the beginning of a sentence), "language", and "LANGUAGE" (in a title in capitals); a case-sensitive search will find the computer language "BASIC" but exclude most of the many unwanted instances of the word. For example, the
337:, because most file systems in other Unix-like environments are case-sensitive, and, for example, a source code tree for software for Unix-like systems might have both a file named Makefile and a file named makefile in the same directory. In addition, some Mac 273:, for example, variable names are case-sensitive but function names are not case-sensitive. This means that if a function is defined in lowercase, it can be called in uppercase, but if a variable is defined in lowercase, it cannot be referred to in uppercase. 92:: Authentication systems usually treat usernames as case-insensitive to make them easier to remember, reducing typing complexity, and eliminate the possibility of both mistakes and 63:, for example, or something with no ambiguity regarding capitalization and ambiguity between two or more terms cut down by capitalization, they may prefer a case-sensitive search. 333:
mode (so that a file created as readme.txt is shown as readme.txt and a file created as Readme.txt is shown as Readme.txt) by default. This causes some issues for developers and
59:, "dog" and "Dog" are of the same significance to them. Thus, they request a case-insensitive search. But when they search an online encyclopedia for information about the 356:
were case-insensitive and not case-preserving, so that a file whose name is entered as readme.txt or ReadMe.txt is saved as README.TXT. Later, with
96:
when two usernames are identical in every aspect except the case of one of their letters. However, these systems are not case-blind. They
106:: Authentication systems usually treat passwords as case-sensitive. This enables the users to increase the complexity of their passwords. 338: 317:
systems, filenames are usually case-sensitive (there can be separate readme.txt and Readme.txt files in the same directory).
130:: Some programming languages are case-sensitive for their variable names while others are not. For more details, see below. 497: 461: 635: 513: 254: 190: 83: 242: 202: 266: 206: 389:
The link "Friendly Fire" must go through the (disambiguation) qualifier in a Knowledge article to avoid a
198: 186: 329:
in a case-insensitive (so that there cannot be a readme.txt and a Readme.txt in the same directory) but
448: 295: 274: 214: 75: 610: 262: 305:, from the idea of folding the character code table so that upper- and lowercase letters coincide. 178: 670: 585: 127: 453: 174: 489: 481: 109: 238: 8: 562: 571: 477: 427: 493: 457: 330: 121: 117: 97: 294:
SQL most operations and searches are case-sensitive by default, while in most other
290:
engine is basically case-insensitive, with no option for case-sensitive search. In
277:
is case-insensitive and ignores underscores, as long as the first characters match.
537: 390: 32: 439: 291: 373:
environments, similar to the problems with macOS case-insensitive file systems.
538:"case-sensitive-search - case sensitive google search - Google Project Hosting" 443: 365: 152:
sections of a URL may or may not be case-sensitive, depending on the receiving
60: 664: 287: 265:, in which the capitalisation of an identifier encodes information about its 79: 93: 364:
the FAT file systems became case-preserving as an extension of supporting
643: 334: 250: 226: 44: 100:
so that users may choose an aesthetically pleasing username combination.
55:). For instance, when users interested in learning about dogs search an 19: 361: 153: 16:
Defines whether uppercase and lowercase letters are treated as distinct
403: 314: 269:. Some other programming languages have varying case sensitivity; in 222: 113: 28: 24: 341:
assume case insensitivity and fail on case-sensitive file systems.
322: 209:). Others are case-insensitive (i.e., not case-sensitive), such as 103: 89: 230: 194: 446:(February 1978). "Chapter 2: Types, Operators and Expressions". 345: 258: 56: 452:(1st ed.). Englewood Cliffs, NJ: Prentice Hall. p.  353: 349: 318: 218: 182: 402:
Although one can explicitly set a single database or column
611:"Case Sensitivity in Subsystem for UNIX-based Applications" 369: 357: 326: 246: 237:(for the syntax, and for some vendor implementations, e.g. 210: 116:
operating systems treat file names case-sensitively while
270: 234: 133: 31:"A" are the two case variants of the first letter in the 71:
Case sensitivity may differ depending on the situation:
86:(capitalized "Fire") returns the disambiguation page. 301:Case-insensitive operations are sometimes said to 321:is somewhat unusual in that, by default, it uses 298:'s SQL searches are case-insensitive by default. 662: 438: 120:is case-insensitive but, for most file systems, 98:preserve the case of the characters in the name 636:"Filenames are Case Sensitive on NTFS Volumes" 564:Oracle SQL Developer User's Guide, Release 1.5 586:"C.5.5.1 Case Sensitivity in String Searches" 168: 177:are case-sensitive for their identifiers ( 476: 561:"2.10 Making Queries Case Insensitive". 488:(1st ed.). O'Reilly Media. p.  432: 66: 18: 164:parts, however, are strictly lowercase. 663: 368:. Later Windows file systems such as 253:. There are also languages, such as 13: 14: 682: 514:"Nim Manual: Identifier Equality" 308: 280: 82:returns the military article but 47:letters are treated as distinct ( 628: 603: 578: 554: 530: 506: 470: 420: 396: 383: 124:. For more details, see below. 1: 413: 642:. 2006-11-01. Archived from 482:"Chapter 2: Language Basics" 7: 10: 687: 590:MySQL 5.0 Reference Manual 449:The C Programming Language 376: 169:In programming languages 45:uppercase and lowercase 36: 175:programming languages 67:Areas of significance 22: 406:to be case-sensitive 239:Microsoft SQL Server 221:(an exception being 478:Matsumoto, Yukihiro 440:Kernighan, Brian W. 241:, the data itself) 572:Oracle Corporation 518:nim-lang.github.io 486:Ruby in a nutshell 444:Ritchie, Dennis M. 313:In filesystems in 37: 640:Microsoft Support 118:Microsoft Windows 112:: Traditionally, 51:) or equivalent ( 678: 655: 654: 652: 651: 632: 626: 625: 623: 622: 607: 601: 600: 598: 597: 582: 576: 575: 569: 558: 552: 551: 549: 548: 534: 528: 527: 525: 524: 510: 504: 503: 480:(January 2002). 474: 468: 467: 436: 430: 424: 407: 400: 394: 387: 53:case-insensitive 43:defines whether 41:case sensitivity 33:English alphabet 686: 685: 681: 680: 679: 677: 676: 675: 661: 660: 659: 658: 649: 647: 646:on Jul 23, 2013 634: 633: 629: 620: 618: 615:Microsoft Learn 609: 608: 604: 595: 593: 584: 583: 579: 567: 560: 559: 555: 546: 544: 542:code.google.com 536: 535: 531: 522: 520: 512: 511: 507: 500: 475: 471: 464: 437: 433: 425: 421: 416: 411: 410: 401: 397: 388: 384: 379: 331:case-preserving 311: 283: 171: 122:case-preserving 69: 17: 12: 11: 5: 684: 674: 673: 671:Capitalization 657: 656: 627: 602: 577: 574:. August 2013. 553: 529: 505: 498: 469: 462: 431: 418: 417: 415: 412: 409: 408: 395: 381: 380: 378: 375: 366:long filenames 310: 309:In filesystems 307: 282: 281:In text search 279: 170: 167: 166: 165: 131: 128:Variable names 125: 107: 101: 87: 68: 65: 61:United Nations 49:case-sensitive 39:In computers, 15: 9: 6: 4: 3: 2: 683: 672: 669: 668: 666: 645: 641: 637: 631: 616: 612: 606: 591: 587: 581: 573: 566: 565: 557: 543: 539: 533: 519: 515: 509: 501: 499:0-596-00214-9 495: 491: 487: 483: 479: 473: 465: 463:0-13-110163-3 459: 455: 451: 450: 445: 441: 435: 429: 423: 419: 405: 399: 392: 386: 382: 374: 371: 367: 363: 359: 355: 351: 347: 342: 340: 336: 332: 328: 324: 320: 316: 306: 304: 299: 297: 293: 289: 288:Google Search 278: 276: 272: 268: 264: 260: 256: 252: 248: 244: 240: 236: 232: 228: 224: 220: 216: 212: 208: 204: 200: 196: 192: 188: 184: 180: 176: 163: 159: 155: 151: 147: 143: 139: 135: 132: 129: 126: 123: 119: 115: 111: 108: 105: 102: 99: 95: 91: 88: 85: 84:Friendly Fire 81: 80:friendly fire 77: 74: 73: 72: 64: 62: 58: 54: 50: 46: 42: 34: 30: 26: 21: 648:. Retrieved 644:the original 639: 630: 619:. Retrieved 617:. 2005-08-22 614: 605: 594:. Retrieved 589: 580: 563: 556: 545:. Retrieved 541: 532: 521:. Retrieved 517: 508: 485: 472: 447: 434: 422: 398: 385: 348:filesystems 343: 312: 302: 300: 284: 172: 161: 157: 149: 145: 141: 137: 70: 52: 48: 40: 38: 428:WP:DIFFCAPS 335:power users 227:Common Lisp 650:2013-05-20 621:2013-05-20 596:2013-05-20 547:2013-05-20 523:2019-04-27 414:References 362:Windows 95 344:The older 339:Installers 154:web server 110:File names 404:collation 391:WP:INTDAB 315:Unix-like 303:fold case 267:semantics 223:BBC BASIC 150:authority 114:Unix-like 104:Passwords 90:Usernames 76:Searching 29:uppercase 25:lowercase 665:Category 146:fragment 27:"a" and 592:. MySQL 255:Haskell 231:Fortran 217:, most 195:Verilog 496:  460:  393:error. 346:MS-DOS 292:Oracle 261:, and 259:Prolog 251:ooRexx 243:Pascal 219:BASICs 203:Python 158:scheme 156:. The 148:, and 136:: The 57:e-book 568:(PDF) 377:Notes 354:FAT16 350:FAT12 319:MacOS 207:Swift 173:Some 142:query 94:fraud 494:ISBN 458:ISBN 426:See 370:NTFS 358:VFAT 352:and 327:APFS 325:and 323:HFS+ 296:DBMS 249:and 247:Rexx 211:ABAP 205:and 199:Ruby 187:Java 162:host 160:and 138:path 134:URLs 23:The 360:in 275:Nim 271:PHP 235:SQL 225:), 215:Ada 183:C++ 667:: 638:. 613:. 588:. 570:. 540:. 516:. 492:. 484:. 456:. 454:33 442:; 263:Go 257:, 245:, 233:, 229:, 213:, 201:, 197:, 193:, 191:C# 189:, 185:, 181:, 144:, 140:, 653:. 624:. 599:. 550:. 526:. 502:. 490:9 466:. 179:C 35:.

Index


lowercase
uppercase
English alphabet
uppercase and lowercase
e-book
United Nations
Searching
friendly fire
Friendly Fire
Usernames
fraud
preserve the case of the characters in the name
Passwords
File names
Unix-like
Microsoft Windows
case-preserving
Variable names
URLs
web server
programming languages
C
C++
Java
C#
Verilog
Ruby
Python
Swift

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.