- Log in to post comments
User bio
xDBC client connectivity - JDBC, ODBC, ADO.Net
Gateway connections - Java, JDBC, ODBC
Entity Framework
Member since Dec 7, 2015
Posts:
Jim has not published any posts yet.
Replies:
Since we provide a IRIS ADO provider, that should be used rather than using Microsoft's ODBC provider. On Unix, Microsoft is linked to a version of unixODBC driver manager that is compiled to use 2 byte Unicode and therefore you must also use a ODBC driver that matches how unixODBC is built. The Microsoft ODBC Provider is not flexible with how it retrieves Unicode, so UTF-8 and UTF-32 drivers that we have don't work for their DotNet implementation. If you use our IRIS provider, there are no issues fetching Unicode data, and you avoid all the extra overhead of jumping between managed (DotNet) code and unmanaged code (ODBC driver manager and driver).
- Log in to post comments
Certifications & Credly badges:
Jim has no Certifications & Credly badges yet.
Followers:
Jim has no followers yet.
Following:
Jim has not followed anybody yet.
You can cast the Connection to IRISConnection.isUsingSharedMemory() to see if the current connection is connected via shared memory.
You can disable it when getting a connection by passing a Property = SharedMemory=false
You can also disable it on a DataSource with setSharedMemory(false)