Re: Non-ASCII Connection String Issues
Hi Gabriela. Thank you for the quick response and for verifying what I am seeing. Just as a suggestion (and perhaps this is what you were already thinking), it seems like the default handshake encoding should be using UTF8 even if it isn't explicitly called out in the connection string so that no users will have issues by default. This would also help existing code bases out there so that they can just pick up the new libraries and use them out of the box without having to change their code to append "charset=utf8" to them. In any case, I think as long as there is a way to control the encoding that would be great. Thanks again!
Elliott
Subject
Written By
Posted
Re: Non-ASCII Connection String Issues
August 14, 2013 04:48PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.