Ed might be right... I was just trying to help you understand what I think to be true:
Usually if you change a Dictionary that an index is built on, you have to rebuild the index for that dictionary. This is especially true on any I-type dictionary. On Tue, Jul 26, 2011 at 2:09 PM, Ed Clark <[email protected]> wrote: > universe or unidata? what flavor? > > I don't see how this would have worked in the first place? When you use a > query with literal comparisons, the literal is compared against the > pre-converted value. If the attribute has a reversible conversion then your > literal will be reverse-converted first, for example: > SELECT INVOICE-FILE WITH INVOICE.DATE = "12/31/2010" > if INVOICE.DATE has a date conversion then "12/31/2010" will be converted > to an internal value before comparison. But in your example MCU is not > reversible. So you will only find what you ask for literally. > > Is it possible that you were using a different attribute that does a > computation? A virtual attribute on unidata or a correlative on universe > with does the upcasing? In that case then your literal in the query would be > compared against the calculated value. An index would also be built on the > calculated value > > On Jul 26, 2011, at 1:37 PM, Chris Austin wrote: > > > > > I changed the DICT entry for field NAME on the CLIENT table to the > following: > > > > NAME > > 0001 D > > 0002 5 > > 0003 MCU > > 0004 Name > > 0005 25L > > 0006 S > > 0007 > > 0008 CHARACTER,25 > > > > But it still doesn't seem to work in regards to the case-sensitive. > > > > Chris > > > > > > > >> From: [email protected] > >> To: [email protected] > >> Date: Tue, 26 Jul 2011 09:44:35 -0700 > >> Subject: Re: [U2] CONV MCU on indexed field? > >> > >> We are using Unidata and this is a dict for Country: > >> > >> CNTRY: > >> > >> D > >> > >> 4 > >> > >> MCU > >> > >> Cntry > >> > >> 6L > >> > >> M > >> > >> > >> You could do the same change to the NAME definition but I was suggesting > >> that if you didn't want to or couldn't do that then another definition > could > >> be created that forced the name to be upper-case. > >> > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Chris Austin > >> Sent: Tuesday, July 26, 2011 9:36 AM > >> To: [email protected] > >> Subject: Re: [U2] CONV MCU on indexed field? > >> > >> > >> > >> I'm not exactly following you. Would this dict item called NAME.UPCASE, > >> would that be a new field to test this or woudl that be a specific field > >> used to do the conversion? What would the dictionary look like. > >> > >> Chris > >> > >> > >>> From: [email protected] > >>> To: [email protected] > >>> Date: Tue, 26 Jul 2011 09:32:48 -0700 > >>> Subject: Re: [U2] CONV MCU on indexed field? > >>> > >>> Could you create another dict item called NAME.UPCASE and put the MCU > >>> in that definition? > >>> > >>> -----Original Message----- > >>> From: [email protected] > >>> [mailto:[email protected]] On Behalf Of Chris > >>> Austin > >>> Sent: Tuesday, July 26, 2011 9:25 AM > >>> To: [email protected] > >>> Subject: [U2] CONV MCU on indexed field? > >>> > >>> > >>> > >>> We've been using the following command to select a name regardless of > >>> how it's capitalized: > >>> > >>> SELECT CLIENT WITH NAME CONV MCU = "BRUCE]" > >>> > >>> However, after I indexed the field NAME on the CLIENT table the same > >>> command only returns the values that match the case-sensitive. In > >>> other words after we indexed the field name it doesn't seem that we > >>> can use CONV MCU, is there a work around to this? > >>> > >>> Thanks, > >>> > >>> Chris > >>> > >>> > >>> _______________________________________________ > >>> U2-Users mailing list > >>> [email protected] > >>> http://listserver.u2ug.org/mailman/listinfo/u2-users > >>> _______________________________________________ > >>> U2-Users mailing list > >>> [email protected] > >>> http://listserver.u2ug.org/mailman/listinfo/u2-users > >> > >> _______________________________________________ > >> U2-Users mailing list > >> [email protected] > >> http://listserver.u2ug.org/mailman/listinfo/u2-users > >> _______________________________________________ > >> U2-Users mailing list > >> [email protected] > >> http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > _______________________________________________ > > U2-Users mailing list > > [email protected] > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- John Thompson _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
