Vincent Rogier

I ran into more tests and found out a way to solve the issue. The Oracle OCI API is a inconsistent when handling indicator structure related to object retrived from...

@cjbj I first wanted to do so and started an mail to you and Anthony but I realized that the issue was between the desk and the computer! I made...

Hi, Autodetecting oracle assets location had never been a feature but rather a best effort. When OCILIB had been first released about 15 years ago, Oracle 8/9/10 was the norm...

Hi, thanks for reporting the issue. XMLTYPE is not supported yet by OCILIB. but your example show a real bug in OCILIB a type info creation fails, it is not...

Hi' Yes, that's what I had in mind when you posted the issue. I will first commit the fix for the regression that does not remove the type info from...

Hi, Thus, some progress here. I have added in v4.7.7 partial support for XMLTYPE :) Now column metadata reports "XMLTYPE" for such column. XMLTYPE column can now be also fetched...

see https://github.com/vrogier/ocilib/blob/develop-v4.7.7/tests/TestREportedIssuesCppApi.cpp ```c++ TEST(ReportedIssuesCppApi, Issue331) { auto expectedString = ToUpper(ostring(OTEXT(""))); Environment::Initialize(); Environment::EnableWarnings(true); Connection con(DBS, USR, PWD); Statement st(con); st.Execute(OTEXT("SELECT XMLELEMENT(\"element\",xmlattributes(('name') as name, ('str') as \"type\")) as xml from dual")); auto...

I will have to do further testing but its seems good so far.

I completely forgot the constraint about LONG with scrollable cursors. I went with LONG + dynamic fetching as: - Host Lobs cannot be used on client side for XMLTYPE (that's...

I made a test selecting 2 XMLTYPES with scrollable cursors and it works :). Thus having 1 LONG columns for scrollable cursors is only on the server side column type,...