Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 8 of 8 total |
NOCASE with WHERE |
Thu, Jun 8 2006 7:16 AM | Permanent Link |
SteveW | It would be nice to be able to use NOCASE with WHERE as well as with ORDER BY
e.g. SELECT MyField1, MyField2 FROM MyTable WHERE MyField1 = 'abc' AND MyField2 LIKE 'x%' NOCASE ORDER BY MyField1, MyField2 NOCASE; |
Thu, Jun 8 2006 8:00 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | SteveW
What's wrong with UPPER? SELECT MyField1, MyField2 FROM MyTable WHERE MyField1 = 'abc' AND UPPER(MyField2) LIKE UPPER('x%') ORDER BY MyField1, MyField2 NOCASE; Bit more typing but works a treat and is easy to spot Roy Lambert |
Thu, Jun 8 2006 8:39 AM | Permanent Link |
SteveW | <<What's wrong with UPPER?>>
You need 2 UPPERs for 1 NOCASE |
Thu, Jun 8 2006 8:49 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | SteveW
>You need 2 UPPERs for 1 NOCASE And I thought I was lazy Roy Lambert |
Thu, Jun 8 2006 8:39 PM | Permanent Link |
"Ralf Mimoun" | SteveW wrote:
> <<What's wrong with UPPER?>> > > You need 2 UPPERs for 1 NOCASE So? In Delphi, I need a begin/end for a {} in C/C++/Java/younameit. Type it once, change it 10 times, read it a thousand times. Typing time is _unimportant_. Ralf |
Fri, Jun 9 2006 3:53 AM | Permanent Link |
SteveW | <<So? In Delphi, I need a begin/end for a {} in C/C++/Java/younameit. Type it
once, change it 10 times, read it a thousand times. Typing time is _unimportant_.>> Why have a combine harvester when you could cut the wheat with a scythe? Laziness is the mother of invention. It also has a nice consistency about it, I can use NOCASE with CREATE INDEX and ORDER BY so why not with WHERE? |
Fri, Jun 9 2006 10:30 AM | Permanent Link |
"Ralf Mimoun" | SteveW wrote:
.... > Why have a combine harvester when you could cut the wheat with a > scythe? > Laziness is the mother of invention. For me, a double UPPER is way more descriptive than a NOCASE somewhere at the end. Make code readable is more important than reducing the keystrokes. > It also has a nice consistency about it, I can use NOCASE with CREATE > INDEX and ORDER BY so why not with WHERE? Because UPPER is standard. More or less every SQL db system use that thing. And because it is clear. You can write WHERE Field1=Field2, WHERE UPPER(Field1) = Fíeld2, WHERE Field1=UPPER(Field2) and WHERE UPPER(Field1) = UPPER(Field2). They all have different meanings. And why do I need two different notations for one function? Ralf |
Mon, Jun 12 2006 3:50 AM | Permanent Link |
SteveW | <<For me, a double UPPER is way more descriptive>>
Then carry on using it, I'm not suggesting doing away with it. <<than a NOCASE somewhere at the end. >> It wouldn't necessarily be at the end, you're not getting the idea... <<You can write WHERE Field1=Field2, WHERE UPPER(Field1) = Fíeld2, WHERE Field1=UPPER(Field2) and WHERE UPPER(Field1) = UPPER(Field2)>> Or you could write: WHERE Field1=Field2, WHERE UPPER(Field1) = Fíeld2, WHERE Field1=UPPER(Field2) and WHERE Field1 = Field2 NOCASE <<And why do I need two different notations for one function?>> There are things you need and things you desire, one of my desires is to use NOCASE with WHERE, ok... |
This web page was last updated on Friday, April 26, 2024 at 06:09 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |