Case-sensitivity (or CASE-sensitivity OR Case-SeNsItIvItY) is a topic of much discussion over the years and there are many different topics over time.
Since 1991, Sybase has supported case-sensitivity at the DB level Since its initial release, MS SQL has supported case-sensitivity at the DB level Since probably 2000, filters and active links in the windows clients have correctly obeyed the DB-case sensitivity rules and all behavior of them have had the qualifiers here matching the DB case sensitivity setting. The web client was found to be not obeying in active links the DB case sensitivity setting and that was corrected in about the 7.5 or maybe 7.6 release (this is the best I can remember which version). Now, we come to Oracle..... This database did not support case-sensitivity for many years. There were all kinds of attempts and partial implementations of this. This included the idea of functional indexes and special handling and the requirement to do special operations and even then, it only worked under some conditions (in = and < and > but not for LIKE). Finally, there is full case-insensitivity support with Oracle and the 8.1 release of the AR System has support for it. It requires special index builds (which the system does for you). It requires that you set cursor sharing to EXACT which requires that you give lots of memory to the DB to compensate for the fact that this is not the best cursor sharing for the AR System in general. But, it does work for all operations and provides complete case-insensitivity for Oracle. So, all aspects of the system everywhere -- from DB operations to server side workflow to client side workflow -- are all correctly obeying the case-sensitive or case-insensitive setting of the DB. And, Sybase, MS SQL, and Oracle all support both a case-sensitive or case-insensitive mode for operation. And, to be clear, when working case-insensitive -- CAT, cat, Cat, CAt, CaT, and any other permutation of upper and lower case letters in the search criteria will match any permutation of upper and lower case letters for the same characters in the data. And, it will work across languages and with all character sets -- including Unicode. I hope this helps clarify this issue. Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Sagar G Anandpara Sent: Thursday, August 29, 2013 10:46 PM To: arslist@ARSLIST.ORG Subject: Re: Enhancements to Developer Studio on ARS v8.1 Hi Kiran, What you gave as a real enhancement (in the Tabular form), was there in v7.6.04 as well, so only I had made the post. What John is telling makes sense but is that the only improvement John? or any more things been improved, and if so, how do they too help? Also, I too would like to know Terry's doubt, what if in Advance Search I enter 'Field1' = "SAGAR" instead of 'Field1' = "sagar" (or say 'Field1' = "Sagar")? Would they give same results or will fail and will return a message saying NO MATCHING RECORDS FOUND? Regards, Sagar _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
