Closed nmoreaud closed 1 month ago
It happens for ADDRESS
and DESCRIPTION
fields.
Thanks. I can replicate the issue. I'll let you know when I have discovered the source of the issue!
Good news! I was able to correct the issue and have pushed a patch that corrects it. If you are able to build from source you can verify that it works for you, too.
Very nice, thanks. Do you also maintain a more "stable" version 1.X branch? If so I would greatly appreciate a fix in this branch too. I am going to test your fix on Monday if I have the opportunity.
2.2.x is considered stable! So I have no plans to add to any of the v1 branches or to create another v1 patch. Is there a reason you are avoiding v2.x?
Okay, I will test if my application works fine with the latest version
The fix works fine for me
This was included in version 2.2.1 which was just released.
If I try to connect to an Oracle server and my connection string is badly formatted (here ADRESS instead of ADDRESS), oracledb raises an internal exception. (note oracledb before 2.0 crashes with a segfault)
Ex: