"We settled on 'TR.Fieldname != $NULL$ AND 'Fieldname' != 'DB.Fieldname'
What's wrong with this?"
Its more complicated than it needs to be. ('Fieldname' !=
'DB.Fieldname') by itself will give you the same results.
By the way, the discussion isn't TR versus DB values, but rather whether
or not there is a need to use the TR values (DB values are useful). My
contention is that using TR values introduces unnecessary confusion and
can cause unexpected results, without any benefit.
I'll drop the topic for now, but if anyone wants to continue the
discussion off-list feel free to email me.
Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard
Bach
"Mike White" <[EMAIL PROTECTED]>
Sent by: "Action Request System discussion list(ARSList)"
<[email protected]>
02/22/2008 08:27 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: Interview questions
**
Hello, Matt!
This TR-vs-DB discussion usually gives me a headache that only a few beers
can cure, but I'll weigh-in, anyway (proving that I can't learn from
history!).
Unless I misunderstood, Richard offered
( 'TR.lesson_status' = "Completed")
as an alternative to
('DB.lesson_status' != "Completed" AND 'lesson_status' = "Completed")
Good point about the db search, but I'd add the obvious - using only the
TR value exposes the Filter to workflow updates. If another Filter pushes
"Completed" to the record, even though it's already populated with
"Completed", the Filter will fire.
We settled on 'TR.Fieldname != $NULL$ AND 'Fieldname' != 'DB.Fieldname'
What's wrong with this? And more to the point, what was wrong with David's
original Run If:
( 'lesson_status' = "Completed" ) AND ( 'DB.lesson_status' != "Completed"
)
I don't see where it would be a problem, either. ('Not sure I understood
how API updates impact it).
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
Carey Matthew Black <[EMAIL PROTECTED]>
Carey Matthew Black <[EMAIL PROTECTED]>
Sent by: "Action Request System discussion list(ARSList)"
<[email protected]>
02/22/2008 10:52
Please respond to arslist
To: [email protected]
cc:
Subject: Re: Interview questions
Actually...
Run If qualifications (for Filters) do not cause "searches" to the DB.
( Which are the only context that the 'TR' vs 'DB' discussion makes
any sense in.) Run If's (for Filters and Active Links) are evaluated
by the ARS application (server or client) and not sent to the RDBMS.
However, Escalations Run If's are sent to the RDBMS as well as
Set/Push field qualifications.
Yes.. Yes... if you reference 'Field' or 'DB.Field' in a Filter Run If
then the record of interest for the transaction is fetched from the
DB. But that is based on 'Entry ID' (Field 1) and is the unique
clustered index on the form so that search is mute. It is the best
that the DB can do and the value of having the DB values at had
generally far out ways the cost of that trip to the RDMBS. (IMHO)
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
On Fri, Feb 22, 2008 at 10:15 AM, McCabe, Richard A. (CMS/CTR)
<[EMAIL PROTECTED]> wrote:
> **
>
>
>
> The following statements would fire the same, but the first statement
would
> be cleaner to read, and more efficient as it would not cause a full
query of
> the table by causing the database to run a "not equal to" search
bypassing
> your indexes. ( 'TR.lesson_status' = "Completed") vs.
('DB.lesson_status' !=
> "Completed" AND 'lesson_status' = "Completed")
>
>
>
> Richard McCabe
>
>
>
>
> ________________________________
>
>
> From: Action Request System discussion list(ARSList)
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___
***IMPORTANT NOTICE: This communication, including any attachment, contains
information that may be confidential or privileged, and is intended solely for
the entity or individual to whom it is addressed. If you are not the intended
recipient, you should delete this message and are hereby notified that any
disclosure, copying, or distribution of this message is strictly prohibited.
Nothing in this email, including any attachment, is intended to be a legally
binding signature.***
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
