You are on page 1of 1

The exist method must: Be static because it is used to check if any table object (record) exists among all

the objects of the table class. Return a boolean value. Take an argument of the type of the key of the table or a list of arguments if the key consists of more than one field. f there is a list of arguments! they must be in the same order as the fields in the index that are used for the table"s key. #heck for the most effective! existing index in the record against the supplied key! and then return true if it is in the table. f not! false. Run on both the client and server. This is the default behavior. $ou can also make it explicit by putting %client server% in the declaration! but do not specify a single tier in the declaration (either the client or the server). The method must be used &henever one record should be checked that is exists based on its key. 'xample The follo&ing code is an example of the static exist method design pattern. static boolean exist(#ust(roup d cust(roup d) ) return cust(roup d ** (select first+nly Rec d from cust(roup index hint (roup dx &here cust(roup.cust(roup ,, cust(roup d).Rec d -, ./ 0

You might also like