[437] in Tooltime
Re: debi/steve thing
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Fri Oct 24 13:21:24 1997
In-Reply-To: <v03020906b07573d4d6ed@[18.81.0.229]>
Date: Fri, 24 Oct 1997 13:25:20 -0400
To: Debi Fuchs <debi@MIT.EDU>
From: Steven Wade Neiterman <wade@MIT.EDU>
Cc: tooltime@MIT.EDU
We went through this when the Scopus consultant was here. My understanding
is that the scopus design application does not allow for adding the
"upper(mit_pri_lastname)" criteria. Thus, search fields that contain mixed
case (firstname, lastname, email) were inserted in uppercase.
..Steve
>
>
>I'm using a wholly different process than Peter did to do the conversion.
>It took a while to set up, but will allow for pretty quick conversion of
>new data. Are you saying I should be converting the names before I export
>them. I can do that if necessary.
>
>Can I ask why it is necessary to store names as uppercase? The scopus
>command for a find "by example" on last name seems to be:
> SELECT mit_log_id "Log", substr(mit_status,1,10) "Status",
> mit_category "Category", mit_pri_lastname "Last Name",
> mit_pri_firstname "First Name" ,
> substr(to_char(mit_created_ts,'YYYY/MM/DD HH24:MI:SS'),1,20)
> "Created On", substr(mit_summary,1,80) "Summary"
> WHERE 0 = 0 and mit_pri_lastname LIKE upper('fuchs')
> order by mit_log_id asc
>
>Is it, for some reason, not possible to set up the find "by example" to
>have the WHERE clause as follows:
> WHERE 0 = 0 and upper(mit_pri_lastname) LIKE upper('fuchs')
>
