[Home] [Help]
161: * o A record and table type to hold the details of the contexts
162: * and database items in the cache. A separate table is used
163: * for contexts and database items. In the case of contexts,
164: * it is indexed directly by the context_id.
165: * o Since FF_DATABASE_ITEMS does not have a surrogate primary key,
166: * the formula compiler generates a hashed value, which is not
167: * guaranteed to be unique. Therefore, the database item cache
168: * is not indexed directly. Instead, there is a 'hash' data
169: * structure that points to the first possible entry in the
186: type dbi_hash_t is table of dbi_hash_r index by binary_integer;
187:
188: type dbi_cache_r is record /* dbi and context info */
189: (
190: item_name ff_database_items.user_name%type,
191: context_level1 binary_integer,
192: context_level2 binary_integer,
193: data_type varchar2(10),
194: dvalue date,
1264: ,p_business_group_id in number
1265: ,p_legislation_code in varchar2
1266: ) is
1267: select u.route_id
1268: from ff_database_items d
1269: , ff_user_entities u
1270: where d.user_name = p_dbi_name
1271: and d.user_entity_id = u.user_entity_id
1272: and (