libzdb-general February 2014

libzdb-general@tildeslash.com

4 participants
2 discussions

CLOB-columns in Oracle DBs always return 'null'.
by Mats Christensen 04 May '15

04 May '15

Hi, It seems like libzdb (probaly) won't handle CLOBs in Oracle DBs very well. When selecting a CLOB directly nothing but the value 'null' is returned, when typecasting the CLOB to ex. VARCHAR2 it works perfectly. The same problem occurs when inserting data to a CLOB. Tests for Oracle also fails because of this. I've tried libzdb 2.8, 2.12 and 3.0, the same problem occurs in all three. This happens with Oracle Instant Client 11,1 11,2 and 12,1. Has anyone else encountered this? Is it a bug in libzdb or Instant Client? Thank you very much! Regards, Mats Christensen

5 9

Re: CLOB-columns in Oracle DBs always return 'null'.
by Volodymyr Tarasenko 03 Feb '14

03 Feb '14

Thanks for the code, I'm checking this case. Looks like blob was not read correctly. Let you know as soon as I get new results. Good luck, Volodymyr! On Saturday, February 1, 2014 3:44 PM, Volodymyr Tarasenko <tvntsr(a)yahoo.com> wrote: Hi, Mats, thanks for the code, I'm going to check it. Good luck, Volodymyr! On Saturday, February 1, 2014 2:52 PM, Mats Christensen <matschristensen(a)gmail.com> wrote: I missed the clob data on the earlier sql, this is correct. On Sat, Feb 1, 2014 at 1:44 PM, Mats Christensen <matschristensen(a)gmail.com> wrote: See the attachment select.c and clob_test.sql > > >Libzdb 3.0 and Oracle Instant Client 12.1 >This setup returns the following for me: > > >mats@x220 ~/libzdb/libzdb-3.0/test $ ./select >This is getString: >this is a varchar (null) >this is another var (null) >This is getBlob: >this is a varchar this is a clob >this is another var this is another clob > > > > >Can you see if it works for you? The problem might be my setup although I've tried two completely different linux setups. > > >Thanks! > > >Regards, >Mats Christensen > > > > > >On Sat, Feb 1, 2014 at 1:12 AM, Jan-Henrik Haukeland <hauk(a)tildeslash.com> wrote: > >ResultSet_getBlob or ResultSet_getString should be interchangeable on a blob or text column. Though of course, if the blob column contains binary data only ResultSet_getBlob should be used to get the correct value. >> >>I should say that a problem with using ResultSet_getString on a blob column was just fixed in Oracle and confirmed fixed in version 3.0. So with one datapoint, the above seems to work. If you want us to investigate, we are also more inclined to do so if you can provide a small test program demonstrating the problem. Or argue in detail why the problem must be in libzdb. >> >>Best regards >>-- >>Jan-Henrik Haukeland >> >> >>On 31 Jan 2014, at 13:36, Mats Christensen <matschristensen(a)gmail.com> wrote: >> >>> >>> I'm not very familiar with Oracle either but it seems like CLOB is for Oracle what TEXT is for Postgres and MySQL. >>> >>> There is a function in the dbmail-code called 'db_result_get_blob', it is used for several things, >>> like '_fetch_headers'. HEADERVALUE is a CLOB.on Oracle and TEXT on Postgres. >>> >>> Perhaps this function should have been used on '_fetch_envelope' too? >>> >>> It will probably be easiest for me to just use getBlob instead, as for upstream, perhaps it's a good idea to use >>> 'db_result_get_blob' for all TEXT/CLOB-fields if it works? >>> >>> Thank you very much for the help! >>> >>> Regards, >>> Mats Christensen >>> >> >>-- >>To unsubscribe: >>http://www.tildeslash.com/mailman/listinfo/libzdb-general >> > -- To unsubscribe: http://www.tildeslash.com/mailman/listinfo/libzdb-general

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

libzdb-general February 2014