Page 1 of 1

OracleException.Offset not serialized

Posted: Thu 08 Sep 2016 08:07
by kamen
Hi.

We use cross-platform bridge in our application. It is employed:
- in 32-bit build to communicate to 64-bit Oracle clients,
- in 64-bit build to communicate to 32-bit Oracle clients.

We serialize/deserialize requests/responses from/to application/bridge. When error occurs (OracleException) in bridge we also send (serialize/deserialize) it to application.

Unfortunately Offset field is not serialized/deserialized. E.g. for "select * from non_existent_table" original exception has Offset=14 (on bridge side), transferred exception has Offset=0 (on application side).

Can anybody help?

We use dotConnect for Oracle Pro version 8.5.464.0.

Regards,
Petr.

Re: OracleException.Offset not serialized

Posted: Fri 09 Sep 2016 13:24
by Pinturiccio
We have reproduced the issue. We will investigate it and post here about the results as soon as possible.

Re: OracleException.Offset not serialized

Posted: Wed 21 Sep 2016 10:58
by Pinturiccio
We have fixed the bug with losing Offset of an OracleException object when performing binary deserialization. We will post here when the corresponding build of dotConnect for Oracle is available for download.

Re: OracleException.Offset not serialized

Posted: Thu 22 Sep 2016 14:23
by Pinturiccio
New build of dotConnect for Oracle 9.1.111 is available for download!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to viewtopic.php?t=34319

Re: OracleException.Offset not serialized

Posted: Tue 27 Sep 2016 06:40
by kamen
Thanks! We will test ASAP.

Re: OracleException.Offset not serialized

Posted: Fri 07 Oct 2016 10:41
by kamen
Tested with 9.1.121 - works.

Thanks a lot!

Petr.