RE: MaxDB fetch into problem with concatenated data in oracle mode with embedded SQL statment in C/C++ programs (correction)

Hi,

Please send me your Precompiler program for analysis.

Regards,

Thomas Simenec
SAP Labs Berlin

-----Original Message-----
From: Elbertus Lochtenberg [mailto:barry@xxxxxxxxxxxxx] 
Sent: Donnerstag, 30. Dezember 2004 13:33
To: maxdb@xxxxxxxxxxxxxxx
Subject: MaxDB fetch into problem with concatenated data in oracle mode
with embedded SQL statment in C/C++ programs (correction)

Dear Reader,
 
After making some tests with the same program and ORACLE, I came to the
conclusion that the concatenated output of MaxDB is similar. 
 
The difference is that in the ORACLE case the output buffer is filled up
with blanks up to the end -1. In the last byte ORACLE puts a NULL. With
MaxDB the output buffer is filled up to the end with blanks and the byte
(output buffer length+1) seems to contain the character "@" as it is the
last variable on the stack. I suppose that this character depend of what
the memory value is on this point  
 
However is seems that MaxDB is not putting the NULL value at the end of
the output buffer, the prove is that if I define another variable on the
stack, following the output buffer host variable and filled with NULLs,
this "@" character is not shown anymore in the output buffer. 
 
Any way there is something different between the output buffer update
between ORACLE and MaxDB concerning the last byte, which in the ORACLE
case is filled with a NULL character, what isn't the case working with
MaxDB in ORCALE mode.   
 
Best regards,
 
Elbertus Lochtenberg
Project Manager
Teleserver S.A.
 
   

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx