Get_num_value not returning correct value

Question

Hello,
I anm developing with Designer/Headstart 9i. I'll try to be clear on my problem. I am using the function get_num_value form one of my table CAPI. Here is the scenario
1. I do a get_num_value and get 2 as a value
2. I update the column to -1.
3. A business rule does not permit the update so I rollback
4. I do the same get_num_value on the column and I get -1
So what is happening is that the function get_num_value is calling a function get_row. The function get_row checks to see if the row has already been fetched and it returns the value in it's cached variables rather than fetching the value with the tapi slct procedure. Even if I put the same_record parameter to false, it's checks the cached variables before the parameter. Here is a test case and this problem occurs with any CAPI table.
serveroutput ON
DECLARE
v1 NUMBER;
BEGIN
v1 := Gem_Lot_Capi.get_num_value('PROFONDEUR',4122263);
dbms_output.put_line('Value before' || TO_CHAR(v1));
UPDATE GEM_LOTS SET profondeur = -1
WHERE id = 4122263;
v1 := Gem_Lot_Capi.get_num_value('PROFONDEUR',4122263);
dbms_output.put_line('Value after' || TO_CHAR(v1));
EXCEPTION
WHEN OTHERS THEN
v1 := Gem_Lot_Capi.get_num_value('PROFONDEUR',4122263);
dbms_output.put_line('Value exception after ' || TO_CHAR(v1));
SELECT profondeur
INTO v1
FROM GEM_LOTS
WHERE id = 4122263;
dbms_output.put_line('Value exception select ' || TO_CHAR(v1));
END;
Value before 21.34
Value EXCEPTION after -1
Value EXCEPTION SELECT 21.34
If anyone has suggestions, I would appreciate it.
Thanks

Answer 1

Yes I did find a solution. We copied the Headstart packages and modified the code of the get_row function. The new version of the function is to always do a fetch in the database using the tapi slct. Here is the function
function get_row
( p_same_record in boolean
, p_id in number
return cg$age_assignations.cg$row_type
-- Purpose Return row identified by Primary Key parameters
-- Usage From get_column_value functions
is
l_row cg$age_assignations.cg$row_type;
l_tbl_index number(10);
begin
l_row.id := p_id;
-- select row from database using TAPI procedure
-- slct procedure will handle non-existing row
cg$age_assignations.slct(l_row);
g_cached_row := l_row;
return l_row;
end get_row;
Since the get_yyy_value functions are not used by the capi itself, there is no risk involed by doing this. As for database performance, there is no difference since the last row fetched is still in memory when doing a second get_yyy_value on the same record, it's the same as using the global variables.
If you need more info, I can have the developper zip the packages he had to copy and modify and send them to you. Just reply to this message and give me you e-mail.