At 12:31 PM 1/23/2004, Elmar Haneke wrote:

>isc_create_blob does give me the 64Bit ID to write into database.
>Writing into Database and reading it Back from there does work ok.
>But, the ID read from the database does differ from the one written
>before.

The blob id you get back when you read a record with a blob in
it is a combination of the relation id of the table, the pointer
page for the relation, and the offset on the pointed-to page that
represents the blob.

The create_blob call has no record context - it hasn't a clue
where or whether you will store a record connected to the blob.
So it returns a distinctive temporary blob id. That id is
converted to a real blob id in the process of storing the record.

> This is a problem for me since I intend to work with cached
>data which currently implys to read the blob with the ID written to
>database.

You may have to cache blobs associated with unstored records
locally.

>How can I transform the ID recieved from "isc_create_blob" to be
>suitable for "isc_open_blob"?

You really can't - it's not a purely mechanical transformation -
well, yes it is a purely mechanical translation, but only from
the point of view of the database internals.

Regards,

Ann