[454] in Tooltime

home help back first fref pref prev next nref lref last post

Re: Addition to "Find Open" functionality

daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Fri Oct 31 07:42:26 1997

In-Reply-To: <v03110701b07ebcd15a2c@[18.81.0.181]>
Date: Fri, 31 Oct 1997 07:46:31 -0500
To: Peter Ragone <pragone@MIT.EDU>, Debi Fuchs <debi@MIT.EDU>
From: Steven Wade Neiterman <wade@MIT.EDU>
Cc: tooltime@MIT.EDU

I have an option to investigate as a LAST resort.

The sql code is stored in an Oracle table.  We could try to alter the code
in the table and not use the Scopus design interface.  This would work only
if the Scopus GUI is presenting the limitation and not the length of the
field in Oracle.

The downside is that it may hinder maintenance as the developer would need
to know to not use the Scopus design interface to review or alter this code.

Let me know how your doing.

Good luck,

..Steve

At 5:47 PM -0500 10/30/97, Peter Ragone wrote:
>Debi,
>
> The quick answer is "maybe". This is because the Scopus GUI will only let
>us enter SQL text of a particular length. We've exceeded that length while
>trying to design a dialog box for the Find Open button that will let the
>user find only the open logs for a particular category. (Meaning find all
>open Helpdesk, or all open Mainframe, etc.)
>
> We're working on getting around this artificial limitation of Scopus'
>interface because obviously there's no inherent limitation to the logic of
>the SQL code. As an example of how we might get around Scopus, perhaps we
>can call the SQL code from a line of TCL or something like that. Scopus has
>us entering all the 'Where' information in a data field that's only 1 line
>high and seems to have a 255 character limit. (Argh).
>
>-Peter
>
>>Peter and David,
>>
>>For the "find open" scripts, can we also augment them to (1) disclude
>>"Frozen" logs which are marked "Close on Thaw" or for which the frozen date
>>is greater than todays date, as well as to (2) disclude "Taken" logs not
>>taken by the current user, i.e.
>>
>>
>>   SELECT l.mit_log_id "Log", l.mit_status "Status",
>>             l.mit_category "Category", l.mit_pri_lastname "Last Name",
>>             l.mit_pri_firstname "First Name" ,
>>             substr(to_char(l.mit_created_ts,'YYYY/MM/DD HH24:MI:SS'),1,20)
>>             "Created On", substr(l.mit_summary,1,80) "Summary"
>>
>>    FROM      mit_logs l, mit_lk_status s
>>
>>    WHERE     l.mit_status = s.mit_status and s.mit_status_flag=1
>>              and (not( l.mit_status = 'CLOSED' or l.mit_status != 'CANCEL'
>>              or (l.mit_status = 'FROZEN' and (l.mit_frozen_flag='Yes'
>>                  or l.mit_frozen_ts >(SELECT sysdate from dual)))
>>              or (l.mit_status = 'TAKEN' and mit_taken_by !=
>>                  (SELECT userid FROM profiles
>>                     WHERE login_name=(SELECT user from dual))))
>>
>>
>>    ORDER BY  s.mit_weight desc, l.mit_modified_ts, l.mit_log_id asc
>>
>>Thanks,
>>-Debi
>>
>>
>>-------------
>>Debi Fuchs, Consultant
>>MIT Information Systems
>>Computing Help Desk Group
>>77 Massachusetts Avenue, 11-319
>>Cambridge, MA  02139
>>(617) 253-7812
>>debi@mit.edu




home help back first fref pref prev next nref lref last post