| Deutsch English Français Italiano |
|
<slrn1013urt.1aev.rotflol2@geidiprime.bvh> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Borax Man <rotflol2@hotmail.com> Newsgroups: comp.os.linux.advocacy Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them Date: Wed, 30 Apr 2025 10:29:17 -0000 (UTC) Organization: A noiseless patient Spider Lines: 29 Message-ID: <slrn1013urt.1aev.rotflol2@geidiprime.bvh> References: <pan$4068a$3910f4f1$8cbecede$9e42905e@linux.rocks> <20250428075602.0000416d@gmail.com> <8UOPP.1839103$BrX.1740657@fx12.iad> <m79tuoF2bf6U2@mid.individual.net> <RWQPP.125643$oJg.52379@fx17.iad> <m7andaF6bbqU1@mid.individual.net> Injection-Date: Wed, 30 Apr 2025 12:29:17 +0200 (CEST) Injection-Info: dont-email.me; posting-host="107c0e1eb3074cf4cdcb050899a40f11"; logging-data="43323"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19IZJMaXoHkVnDxycyMIdA6jBBSTu0pmqI=" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:+CC5v0XYjFCli232Qq2oefTQ1BE= On 2025-04-29, rbowman <bowman@montana.com> wrote: > On Mon, 28 Apr 2025 15:46:56 -0400, CrudeSausage wrote: > >> The biggest issue I envision anyone having with case sensitivity is not >> remembering what they saved a certain file as. However, if you know that >> the document deals with green eggs, searching for it despite not >> remembering the document filename should be trivial. > > I was talking about databases. In DB2 > > 'SELECT author FROM books WHERE title LIKE 'green eggs%' > > is only going to match 'green eggs' exactly. If you're not sure how the > record was stored you would need LOWER(title). > > The equivalent directory search would be something like > > find . -name "*.txt" | xargs grep -i "green eggs" > > The difference is the directory search is probably going to be a one-shot. > The SQL statement may be executed thousands of times and LOWER() is > costly. > > I'm curious how SQL Server or Access handles case insensitivity in the > internals. However it's done it's faster than explicit conversions at > runtime. Why not just use the -iname option for find? Its the same as -name, but not case sensitive.