topic Native SQL buffering in Application Development and Automation Discussions

Native SQL buffering

NigelJames180 — Mon, 31 Oct 2005 17:32:30 GMT

Hi We are doing some native sql in EXEC SQL ENDEXEC statments to get information from a non SAP source to import into SAP.

Problem is it seems to be buffered in some way. After deleting a record from the oracle windows client and rerunning the ABAP program it picks up data that was just deleted. Is there anyway to select without using any buffers or cache that oracle might be using?

Also a native delete seems to not work. Do we need to do a exec sql. commit work. endexec. ?

Thanks in advance,

Nigel

Re: Native SQL buffering

Former Member — Mon, 31 Oct 2005 18:15:37 GMT

If you are using ABAP SELECT statement, then you have an option 'BYPASSING BUFFER'. See the example below from help.


DATA: WA_SPPROD TYPE SPPROD. 

SELECT * FROM SPPROD INTO WA_SPPROD BYPASSING BUFFER 
         WHERE PRODUCER = 'BOE'. 
  WRITE: / WA_SPPROD-STREET, WA_SPPROD-NUMB, WA_SPPROD-POSTCODE, 
           WA_SPPROD-CITY, WA_SPPROD-COUNTRY. 
ENDSELECT.

Regards,

Srinivas

Re: Native SQL buffering

NigelJames180 — Mon, 31 Oct 2005 20:22:16 GMT

Sorry this did not answer the question. I was asking about NATIVE SQL. As in...

EXEC SQL.

ENDEXEC.

regards,

Nigel

Re: Native SQL buffering

Former Member — Mon, 31 Oct 2005 20:29:42 GMT

I thought your DELETE is in EXEC SQL whereas your SELECT in the ABAP program uses normal ABAP SELECT statement. Is that not correct? Why are you using native SQl for both DELETE and SELECT? Is your table a non-SAP table?

If that is the case then may be COMMIT is what is missing. I don't know if ORACLE also has some kind of buffering.

Srinivas

Re: Native SQL buffering

NigelJames180 — Tue, 01 Nov 2005 11:56:28 GMT

It turns out that a commit was what was missing.