Misi:
Thank you for the clarification of DB.field vice field and access to the database. Looks like the proper use of indexing is paramount for performance.
James McKenzie
L-3 GSI
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Misi Mladoniczky
Sent: Monday, August 28, 2006 1:23 PM
To: [email protected]
Subject: Re: How to verify if the current value entering exists on the database
I guess that you can use the TR-value if you like, but is usually not required.
You could use either of these syntaxes with the same result:
('field' != 'DB.filed' AND 'field' != $NULL$) ('field' != 'DB.filed' AND 'TR.field' != $NULL$)
Depending on what client and version you are useing, fields could be sent even if it is not changed. It could be an active link that set the field to the same value as it had before.
The typical situation would be a Modify All, where the TR-value is set regardless of the database value.
An API-program could of course sen whatever it likes.
In regards to performance, to use the 'DB.field' or 'field' will allways access the database. If you only use 'TR.field' it will not access the database.
Note that all the DB-values needed in the filter run-if-clause will be retrieved in a single database call. In other words, the impact of using 'DB.field' is not that great. The server will typically have to get at least a couple of DB-values anyway.
__20060125_______________________This posting was submitted with HTML in it___
