Vincent Rogier

Hi, This is not a bug but rather an oracle limitation. Oracle varchar/varchar2 types are limited in length in both PL/SQL and SQL engines. It cannot be greater than 4k...

Hi, binding host variables for clob columns shall not use strings but ocilib::clob (despite it works for clob content that is less than varchar max size) Best regards, Vincent

Hi, Having multiple connections working on same db and tables is not an issue. In multithreaded applications, you must use ocilib::Environment::EnvironmentFlags::Type::Threaded. This ensure that some internal containers (like the container...

Hi, Can you provide more information about the performance decrease due to using OCILIB/OCI in multithreaded mode ? Of course, mutexing some calls have indeed an impact but it should...

The API has no way to find out if the user code restrains it self to make calls from same thread or not. The bottleneck you see is not in...

While there is no real need, in this case, to have the handles for the columns to be in a global shared pool (and also columns handles are not created...

Hi, From the profiling on your use case, what was the most expensive locking ? The overhead of the C++ API (over the C one) is the mecanism I implemented...

Hi, I'll commit something that you could test in v.4.7.5 branch before the end of the week. Regards, Vincent

Hi, I made a draft implementation that I committed in v4.7.5 branch. Instead of having a global handle store that is protected when using threaded envs, there are multiple handle...

the C Handles wrapping and tracking mechanism put in place 10 years, while working well, is not very well designed (kind of clumsy). And also, at that time, pre C++11...