Subject | Firebird API calls |
---|---|
Author | gtm2 na interia.pl |
Post date | 2007-10-24T17:56:19Z |
Hello,
I have a question about following situation occured in API calls:
after call of isc_create_blob or isc_create_blob2 in
ISC_QUAD is returned a blob ID (for example
gds_quad_high = 0 and gds_quad_low = 11),
thereafter, this value is placed into sqldata of the
corresponding item of XSQLVAR array in XSQLDA structure,
and finally isc_dsql_execute_immediate is called with
the appropriate sql statement (INSERT... or UPDATE...).
When the updated or inserted record is fetched, the blob
field contains not the value obtained from isc_create_blob
call but totaly different (for example gds_quad_high = 128
and gds_quad_low = 10). Could You please explain it for me
if it is an error or an intended manner of API calls, and
if so then why ? It is very important, because since
isc_create_blob returns only a kind of temporary value of
ISC_QUAD ( blob ID ), the newly inserted or updated record
must be fetched immediatelly in order to obtain the correct
value of blob ID that is required in call of isc_open_blob.
Regards
Gregor Markowski
-----------------R--E--K--L--A--M--A-----------------
Lepsze wiadomosci z kraju i z zagranicy.
Nie wierzysz? Sprawdz - http://wiadomosci.interia.pl/
I have a question about following situation occured in API calls:
after call of isc_create_blob or isc_create_blob2 in
ISC_QUAD is returned a blob ID (for example
gds_quad_high = 0 and gds_quad_low = 11),
thereafter, this value is placed into sqldata of the
corresponding item of XSQLVAR array in XSQLDA structure,
and finally isc_dsql_execute_immediate is called with
the appropriate sql statement (INSERT... or UPDATE...).
When the updated or inserted record is fetched, the blob
field contains not the value obtained from isc_create_blob
call but totaly different (for example gds_quad_high = 128
and gds_quad_low = 10). Could You please explain it for me
if it is an error or an intended manner of API calls, and
if so then why ? It is very important, because since
isc_create_blob returns only a kind of temporary value of
ISC_QUAD ( blob ID ), the newly inserted or updated record
must be fetched immediatelly in order to obtain the correct
value of blob ID that is required in call of isc_open_blob.
Regards
Gregor Markowski
-----------------R--E--K--L--A--M--A-----------------
Lepsze wiadomosci z kraju i z zagranicy.
Nie wierzysz? Sprawdz - http://wiadomosci.interia.pl/